Pinned Tweet
🦀Introducing tokio-netem – network emulation building blocks for Async Rust.
Most tests assume a perfect network. Production… doesn’t.
Wrap any AsyncRead/AsyncWrite to simulate latency, jitter, bandwidth caps, loss, reordering, corruption, abrupt closes, and more. Examples:
A fast, globally distributed KV store. I was lucky enough to work on it. Really cool to see Quicksilver now powering Workers KV Instant and becoming available to developers 🚀
we have this crazy key-value store at Cloudflare called Quicksilver
instantly updates keys across our whole network. microsecond reads from every location. stupid fast
our customers have asked us for years to make it available
we finally did – in a way we think is quite simple - as a new mode for Workers KV
Workers KV Instant
blog.cloudflare.com/workers-…
⚙️ Union and Sum types – do you know the difference?
Both are “A or B”, but Union types merge values while Sum types keep variants distinct.
Rust enums are sum types.
More detail in great post viralinstruction.com/posts/u…
#rust #rustlang
Viacheslav Biriukov retweeted
How does a large language model run on hardware?
A large language model can feel like magic if your background is in CPU-centric programming. That's because the models combine deep neural network with the transformer architecture with a massively parallel processor, GPU, they run on. Furthermore, although you can express a large language model in a few hundred lines of Python, it calls into large, complex layers of software that are hard for a single person to grasp.
To answer this question for myself, I implemented the Qwen3-0.6B model from scratch, from transformer to ISA simulator, with help from Claude Code as a weekend hack. That is, I implemented the model, the GPU instruction set, a compiler, and a GPU simulator to make every layer small enough for one person to understand deeply. I also have RTL for the GPU in the works to run the system on an FPGA, and perhaps in the future, tape it out to actual silicon just for fun.
What's cool is that you can use it like Claude or Codex, but it runs on the CPU and is therefore fully debuggable and traceable. If you have had trouble connecting the dots between large language models and the GPUs they run on, check out the GitHub repository: github.com/penberg/titania
🦀 Rust: How Cloudflare saved 100 TB of DNS cache memory.
Fewer allocations, tighter layout: replace Vec with Box, remove repeated data, and pack records into a contiguous byte buffer.
Result: 56% less memory per entry and 19% faster lookups.
blog.cloudflare.com/dns-cach…
#rust #rustlang
Viacheslav Biriukov retweeted
Went back and finished my Viewstamped Replication implementation in Rust. Protocol only, I/O is provided by the caller. Verified with a TigerBeetle-style simulator. Now thinking about doing some verification with Lean...
github.com/penberg/vsr-rs
🦀 Rust: Pinning in Rust – yet another explanation.
Building Pin from scratch and connecting it to Unpin, self-referential futures, and Future::poll.
gmcgoldr.github.io/2026/08/2…
#rust #rustlang
🐹 Go: How `select` statement actually works under the hood
Dive into the compiler and runtime magic with Jesus Espino in this deep dive! From randomization to locking strategies, discover how Go handles concurrency with precision.
youtu.be/fH5hoZJL_tQ
#go #golang
🦀 Rust: To Async or Not to Async?
A great dive into building an MCP server for rust-analyzer without Tokio:
• 1:1 stdio vs 1:N network I/O
• 3 OS threads instead of an async runtime
• < 2ms cold starts & deterministic teardown
developerlife.com/2026/08/22…
#rust #rustlang
🐹 Go: a must-read deep dive into data races and the memory model
Why code that works can still be wrong:
• memory visibility between goroutines
• compiler & CPU reordering
• happens-before guarantees
• atomics, mutexes, channels
func25.dev/posts/go-memory-v…
#golang #go
⚡️ Zig: Through the Eyes of a Rust Developer
A great comparison from Boris Zhguchev after rebuilding a real Rust project in Zig:
• explicit allocators
• manual ownership
• flatter code
• fewer abstractions
besok.github.io/posts/what-z…
#zig #rust
Migrating from Go 🐹 to Rust 🦀
A great practical guide for Go developers moving to Rust: how familiar Go patterns map to Rust, what changes with ownership, Option, Result, traits and concurrency.
corrode.dev/learn/migration-…
#rust #rustlang #golang #go
🦀 Rust: Tokio spawned first doesn’t mean polled first
A great practical write-up showing what happens when you throw ~1M tasks at Tokio: scheduler fairness, task ordering, memory spikes,and why concurrency needs application-level bounds
pranitha.dev/posts/tokio-giv…
#rust #rustlang
☸️ Kubernetes: a must-read for controller authors.
A great deep dive into what really happens behind r.Get() and r.List(): informer caches, stale reads, memory usage, and the internals that make controller-runtime scale.
kubernetes.io/blog/2026/07/2…
#kubernetes #golang #go
⚡️ Every Software Engineer Should Know SIMD
An awesome post from Mitchell Hashimoto about practical SIMD patterns: take a hot loop, process N values at once, then handle the tail.
mitchellh.com/writing/everyo…
#SIMD #performance
🦀 Rust: Pin and Unpin – another explanation.
A great practical explanation of what pinning actually means, why it exists, and when you need it.
vrong.me/blog/what-is-pinnin…
#rust #rustlang
🐹 Go: fire-and-forget goroutines
“Never start a goroutine without knowing how it will stop.” Dave Cheney.
A great practical take on this maxim: supervised fire-and-forget goroutines with bounded concurrency, panic recovery, and shutdown.
rednafi.com/go/supervised-fi…
#go #golang
🦀 If you are trying to understand modem software development.
bun.com/blog/bun-in-rust
#rust #rustlang
🐹 Go: golps + MCP
gopls now has experimental MCP support, exposing Go-aware LSP features directly to AI assistants.
Agents can ask the language server for real context: packages, symbols, diagnostics, edits, not just grep over files.
go.dev/gopls/features/mcp
#go #golang #mcp
🐹 Go: Zero Copy & io.Copy.
A great post about sendfile, splice, and how to debug and understand what's going on under the hood.
The only part is missing, from my point of view, is a comment about TLS sockets: no sendfile possible for them.
segflow.github.io/post/zero-…
#go #golang
















