Get the weekly digestSubscribe

/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

Yelpremove filterGoremove filterFly.ioremove filterClear all

  1. 01Go · performance

    Better HTTP/1 connection reuse

    Failing to read an HTTP/1 response body completely prevents connection reuse, forcing clients to repeatedly pay the high cost of TCP and TLS handshakes. While developers previously had to implement complex manual body-draining logic, Go 1.27 introduces automatic asynchronous response draining in the net/http package. This improvement allows developers to simply close response bodies without worrying about connection pooling performance.

    DEPTH ■■■■■7 min read11 days ago

    Sign in to save and rate

  2. 02Fly.io · migration

    SBD: We Have a Filesystem at Home

    Fly.io replaced a custom JuiceFS-based filesystem for their Sprites infrastructure with the Sprites Block Device (SBD) to eliminate complex, out-of-sync metadata ledgers. SBD presents object storage as a block device over NBD, allowing standard ext4 to manage the filesystem and simplifying checkpoints and restores. The result is significantly improved reliability and a much simpler storage architecture.

    DEPTH ■■■■■6 min read3 days ago

    Sign in to save and rate

  3. 03Go · architecture

    Arch-specific SIMD in Go

    Go 1.27 introduces the archsimd package to provide low-level architecture-specific SIMD intrinsics for amd64, arm64, and wasm without requiring assembly. The API uses sensible naming conventions, zero-cost type reinterpretation, and opaque masks to improve usability and maintainability while achieving high performance. The resulting design enables developers to write optimized vectorized code safely with proper runtime CPU feature checking and compiler optimizations.

    DEPTH ■■■■■12 min read3 weeks ago

    Sign in to save and rate

  4. 04Yelp · architecture

    The making of the Yelp Assistant UI

    Yelp developed a chat interface called Yelp Assistant using a hybrid approach combining native UI components and a server-driven UI framework called CHAOS. This architecture allows the team to dynamically update the chat experience without waiting for app store releases. The system separates views from data using reactive datasets and MessageEvents to manage the chat loop, state, and user interactions.

    DEPTH ■■■■■12 min read3 weeks ago

    Sign in to save and rate