GitOps 2.0 THE FUTURE OF DEVOPS Table of Contents 1. The Pains of GitOps 1.0 1.1. GitOps tools 1.2. Splitting CI and CD 1.3. Promotion of releases between environments 1.4. Modeling multi-environment

Microsoft Ignite OAM, dapr, and rudr The future of cloud native applications Mark Russinovich @markrussinovich Open Application Model dapr: Distributed Application Platform Building Cloud Scale,

Lifetime Safety Profile • Herb plans to revise the Lifetime Safety Profile as part of Cpp2Future of C++?Future of C++? C++ Core Guidelines’ Lifetime Safety ProfileFuture of C++? C++ Core Guidelines’ Simplified borrowing Hylo (formerly Val): Mutable Value SemanticsSwift’s Law of Exclusivity Future of C++? C++ Core Guidelines’ Lifetime Safety Profile Crubit: Adopting Rust’s Type System Simplified borrowing Hylo (formerly Val): Mutable Value SemanticsSwift’s Law of Exclusivity Future of C++? C++ Core Guidelines’ Lifetime Safety Profile Crubit: Adopting Rust’s Type System

FILE I/O: PAST, PRESENT AND FUTURE CPPCON OCTOBER 3RD 2023 GUY DAVIDSON @HATCAT01INTRODUCTIONS • Head of Engineering Practice at Creative Assembly • 1980 – Acorn Atom • ISO/IEC JTC1/SC22/WG21 • BSI buffered file IO? • How do we optimise unbuffered file IO? • How might the standard help us in future?AGENDA • Sub-megabyte days • More RAM, more disk capacity • Moving data into and out of RAM • buffered file IO? • How do we optimise unbuffered file IO? • How might the standard help us in future?SUMMARY • https://wg21.link/p1040 • https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3017.htm

The Future of Cloud Native Applications with Open Application Model (OAM) and Dapr @markrussinovich Application models Describes the topology of your application and its components The way developers

Building a central Go modules repository: GoCenter’s back to the future. @jfrog @ankushchadha111 GopherCon 2019 Lightning Talk Ankush Chadha About me • Dev Manager, Community & Partner Engineering

Shaping its Future Dan Romlein UX Designer, Google Spencer Sugarman UX Researcher, Google Talk Goals 1. What Dashboard is and why you should be using it 2. Research findings and the future of Dashboard Migrating metrics from Heapster to Kubernetes Metrics API (#2986) ● Apps list page (#2980) Demo Future of Dashboard How do people use Dashboard today, and want to use it tomorrow? https://unsplash

tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support tornado.options — Command-line parsing tornado.testing — Unit it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do everything they are returning). There are many styles of asynchronous interfaces: Callback argument Return a placeholder (Future, Promise, Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which

tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support tornado.options — Command-line parsing tornado.testing — Unit it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do everything they are returning). There are many styles of asynchronous interfaces: Callback argument Return a placeholder (Future, Promise, Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which