said it?Frederick Brooks Jr. • Joined IBM in 1956 • Manager for the development of the IBM System/360 family of computers and the OS/360 software package • In 1975, published The Mythical Man-Month: the essence of the software problem • Buy versus build • Requirements refinement and rapid prototyping • Incremental development – grow, not build, software • Great designersRequirements refinement refinement and rapid prototyping • The hardest single part of building a software system is deciding precisely what to build • The most important function that software builders do for their clients is the

op Source: https://news.itsfoss.com/system76-rust-cosmic-desktop/ 2.1.2 System76-Scheduler II. Practicing Sparrow  https://github.com/pop-os/system76-scheduler Auto-configure priorities for improved desktop responsiveness.  https://www.phoronix.com/scan.php?page=news_item&px=System76-Scheduler-1.1 2.2 Rust for Cloud Native II. Practicing Sparrow  https://rust-cloud-native implemented in Rust: III. Sparrow Development build the Renode Rust UART peripheral example: cargo build --target wasm32-unknown-unknown --release --lib III. Sparrow Development

Visit https://aka.ms/cpp/20 for more details Developer inner-loop C++20 in Visual Studio Build Debug Edit Code Navigation ☑️� Linters ☑️� Colorization & Formatting ☑️� IntelliSense ⌛; ☑️�MSVC installation • Built from source, on-demand • Centralized, tested catalog (no version conflicts) • Popular build targets supported by default, and you can add your own custom targets 🚀 https://vcpkg io continuous integration system Visit https://aka.ms/vcpkg/team for more details Demo CMake integration CMake is a first-class project system in Visual Studio Familiar edit-build-debug inner-loop • including

names, same name in multiple modules will not clash  Modules are processed only once  faster build times  Preprocessor macros have no effect on, and never leak from, modules  Order of module imports “importable”, e.g.  import ;  Everything in is exported, including macros  Improves build throughput; will be processed only once  Comparable to precompiled header files (PCH) { for (int i { startValue }; i < startValue + numberOfValues; ++i) { time_t t { system_clock::to_time_t(system_clock::now()) }; cout << std::ctime(&t); co_yield i; } } int main() { auto

and when work should happen … including some standard ones: an event loop, portable access to the system execution context, nursery for spawned work4 P2300: STD::EXECUTION Proposes: • A set of concepts ☹ the greatest keyboard ever made….82 The mission: Write a program that monitors the entire system for keyboard events and plays Model M clicky sounds.83 MODEL M SIMULATOR: STRATEGY 1. Model Profit!84 Step 1: Model key click as a sender85 MODEL KEYCLICK AS SENDER: STRATEGY 1. Assume system API for registering keyboard callback 2. Write a keyboard sender and op state such that: •

and tested • Released VS 2019 16.5, 16.6, 16.7, 16.8 Preview 3 • GitHub migration ongoing • Build system (native desktop), test suite, issue database • Goal: Complete C++20 in 2020 • No promises, but Generated via GitHub's GraphQL API29 Code: github.com/microsoft/STL • Product: stl/inc, stl/src • Build system: CMake/Ninja • vcpkg submodule acquires Boost.Math for Special Math • tests/std, tests/libcxx

Rust-VMM Why we love Rust-VMM? Rust-VMM is an open-source project that empowers the community to build custom Virtual Machine Monitors (VMMs) and hypervisors. It abstracts the common virtualization • Google implements the first Rust-based light VMM called CrosVM which is in Fuchsia operating system • AWS develops his own light VMM called Firecracker which is based of CrosVM • There are lots acpi linux-loader kvm-ioctls vm-virtio vsock net VFIO APIC vhost Cloud Hypervisor KVM File System Device Driver Host Linux Kernel vCPU block Memory Guest VM containerd + Kata-runtime create

Are Continuous Integration system scales greatly Aware of issues in 10 to 30 min per app Heavily testing on pull requests Numbers > 10 real test devices > 15 build machines (10 OS X, 4 Linux, 3

0 章：命令行小技巧 传统的 CMake 软件构建 / 安装方式 • mkdir build • cd build • cmake .. • make -j4 • sudo make install • cd .. • 需要先创建 build 目录 • 切换到 build 目录 • 在 build 目录运行 cmake < 源码目录 > 生成 Makefile • 执行本地的构建系统 提供了更方便的 -B 和 --build 指令，不同平台，统一命 令！ • cmake -B build • cmake --build build -j4 • sudo cmake --build build --target install • cmake -B build 免去了先创建 build 目录再切换进去再指定源码目录的麻烦。 • cmake --build build 统一了不同平台（ devenv.exe ） • 结论：从现在开始，如果在命令行操作 cmake ，请使用更方便的 -B 和 --build 命令。 // 在源码目录用 -B 直接创建 build 目录并生成 build/Makefile // 自动调用本地的构建系统在 build 里构建，即： make -C build -j4 // 调用本地的构建系统执行 install

不会自动更新，还是旧的那几个文件，可能出现 undefined symbol ，需要重新运行 cmake -B build 才能更新。 • 加了，则每次 cmake --build 时自动检测目录是否更新，如果目录有新文件了， CMake 会自动帮你重新运行 cmake -B build 更新 myvar 变量。 六、头文件和源文件的一一对应关系 • 通常每个头文件都有一个对应的源文件，两个文件名字应当相同 D:/Qt5.12.1/msvc2017/lib/cmake/Qt5 。有三种设置方法： • (1) 单次有效。在 configure 阶段，可以从命令行设置（注意要加引号）： • cmake -B build -DQt5_DIR=”D:/Qt5.12.1/msvc2017/lib/cmake/Qt5” • (2) 全局启用。右键“我的电脑” ->“ 管理” ->“ 高级”添加一个环境变量 Qt5_DIR Qt5_DIR 为 /opt/Qt5.12.1/lib/cmake/Qt5 。有三种设置方法： • (1) 单次有效。在 configure 阶段，可以从命令行设置： • cmake -B build -DQt5_DIR=”/opt/Qt5.12.1/lib/cmake/Qt5” • (2) 全局启用。修改你的 ~/.bashrc 文件添加环境变量： • export Qt5_DIR=”/opt/Qt5