## webpack THE PAST THE PRESENT THE FUTURE TOBIAS KOPPERS GITHUB @SOKRA TWITTER: @WSOKRA ## THE PAST PROBLEMS BUNDLER SOLVE A SHORT WEBPACK HISTORY LESSON ## PROBLEMS BUNDLERS SOLVE • SCRIPT TAGS ts/f/4/a/a/f4aa343a5d22a3384a13c94a17baf10c/p23_2.jpg) Runtime Modules for runtime code ## THE FUTURE WHERE IS WEBPACK HEADING TO? WEBPACK SHOULD BE ![Image](/uploads/documents/f/4/a/a/f4aa343a5d2

### 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

[Image](/uploads/documents/7/8/e/d/78edb81a9976122a3d4c851701bf9145/p1_2.jpg) ## OAM, dapr, and rudr The future of cloud native applications Mark Russinovich CTO, Microsoft Azure @markrussinovich BRK3098

## 20 23 October 01 - 06 ## +23 ## Lifetime Safety in C++: Past, Present and Future #### GABOR HORVATH Gabor.Horvath@microsoft.com ## Welcome to CppCon 2023! Come by our booth and join #visual_studio & Security: The Future of C++ JF Bastien  ## All the Safeties 2023 Safety & Security: The Future JF Bastien 2023 ments/9/d/0/5/9d05b80becbd0a2aac297caf075ed3c2/p8_1.jpg) ## 2023 ## Safety & Security The Future  JF Bastien National

+23 ## File I/O for Game Developers: Past, Present, and Future ## GUY DAVIDSON ## 20 23 October 01 - 06 # FILE I/O: PAST, PRESENT AND FUTURE CPPCON OCTOBER 3 $ ^{RD} $ 2023 GUY DAVIDSON @HATCAT01 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

## Microsoft Ready ## The Future of Cloud Native Applications with Open Application Model (OAM) and Dapr Mark Russinovich Chief Technology Officer, Microsoft Azure @markrussinovich ## Application models Credits: Alex Tai/SOPA Images/LightRocket via Getty Images / Getty Images ## OAM, dapr, and rudr The future of cloud native applications ![Image](/uploads/documents/b/c/2/9/bc29b5fbf1de02f8968a900b84d384e5/p6_4

## Building a central Go modules repository: GoCenter's back to the future GopherCon 2019 Lightning Talk Ankush Chadha 

是否需要另一种“色彩”的 Future?  郭子兴，字节跳动服务框架团队研发工程师。 ## 标题 ## Rust 是否需要另一种“色彩”的 Future? Rust 编译器将 async 块翻译成由标准库提供的 Future 类型，用户可以方便地通过自定义 类型，用户可以方便地通过自定义 Future 以实现非阻塞的 IO 或并发控制语义。异步执行器被允许在任意时刻删除生成的 Future 实例以取消正在执行的异步操作，但取消总是无副作用的吗？Rust 是否需要另一种“颜色”的 Future 为有副作用取消的异步行为提供安全保证？ ## 目录 ## # 基于 Poll 的 Future # 不再是无副作用的取消 # 最终与折中方案 回顾如何使用 Future 支持基于 io-uring 等异步模型让 Future 的取消不 IO，以及基于取消 Future 的流程控制 引入另一种“颜色”的 Future 以最终解决 再无副作用，这可能导致严重的错误 问题，或者基于字节跳动开源的异步驱动 器 monoio 探索的折中方案 ## Rust 中的异步 Rust 基于 Future trait 实现异步编程 pub trait Future { type

Shaping its Future Spencer Sugarman UX Researcher, Google Dan Romlein UX Designer, Google ## Talk Goals 1. What Dashboard is and why you should be using it 2. Research findings and the future of Dashboard Coffee mug $20  ## Future of Dashboard  How

support in C++20. ## std::future ## C++ Concurrency support library std::future ## std::future

Defined in header <future>
template< ; class T > class future;	(1)	(since C++11)
template< class T > class future<T&>	(2)	(since C++11)
template< d>template< class T > class future<void>	(3)	(since C++11)

## Promise: sender Future: receiver ![Image](/uploads/documents/c/e/8/d/ce8