<h2>Must know</h2>
<ul>
<li><strong>Rust infrastructure team delivers major updates</strong>: The Rust Infrastructure Team wrapped up Q4 2025 with a bang, migrating to a new CI bot, moving <a href="http://crates.io" target="_blank" rel="noopener nofollow">crates.io</a> and <a href="http://docs.rs" target="_blank" rel="noopener nofollow">docs.rs</a> to Fastly CDN, and slashing rustc-perf benchmark latency by half. They also renamed default branches across 14 repositories and beefed up Triagebot. For Q1 2026, they’re focusing on <a href="http://docs.rs" target="_blank" rel="noopener nofollow">docs.rs</a> modernization and external hardware CI policy, showing a clear commitment to performance and stability, as reported by the Inside Rust Blog. <a href="https://app.daily.dev/posts/m2OVQmP6S" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Bun runtime shines in microservice benchmarks</strong>: Bun, the JavaScript runtime built with Zig, is flexing its muscles in microservice benchmarks, hitting 157ms mean response times and 6,400 requests per second. That’s about 5x faster than Node.js/Express.js in response time. It’s all thanks to JavaScriptCore optimizations, a native HTTP server, and Linux’s io_uring. This puts Bun right up there with Rust-based frameworks, proving that Zig is a solid foundation for high-performance JavaScript. <a href="https://app.daily.dev/feed-by-ids?id=MJU0O3aRy&amp;id=TXlo2QmbL&amp;id=UYiJEhl6D&amp;id=wx4br4Zyw" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Go’s most popular dependency revealed</strong>: Turns out, <code>github.com/stretchr/testify</code> is the most popular dependency in the Go ecosystem, with a whopping 259,237 dependents. This insight comes from a deep dive into 40 million modules and 400 million relationships using Neo4j. It’s a good reminder that even with new tools, some old habits die hard, as deprecated libraries like <code>pkg/errors</code> are still widely used. <a href="https://app.daily.dev/posts/heMEIyzLQ" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
<h2>Good to know</h2>
<ul>
<li><strong>Bifrost: a lightning-fast LLM gateway in Go</strong>: Bifrost, an open-source LLM gateway written in Go, claims to be 40x faster than LiteLLM with just 11 microseconds of overhead at 5,000 requests per second, offering unified access to 15+ LLM providers. <a href="https://app.daily.dev/feed-by-ids?id=hMdRldhlT&amp;id=P8RYoHcNL&amp;id=ZcbQI1KKZ&amp;id=lqqfnNpcw" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Zig-based DOM implementation for Lightpanda</strong>: Lightpanda replaced its LibDOM with a custom Zig-based DOM called zigdom, aiming for a more cohesive codebase and optimized memory layout, even if performance gains are currently modest. <a href="https://app.daily.dev/posts/2bMcNaDEA" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>TigerBeetle: a specialized financial database in Zig</strong>: TigerBeetle is a high-performance financial database written in Zig, designed for write-heavy workloads with strict serializability, using Viewstamped Replication and direct I/O for extreme resilience. <a href="https://app.daily.dev/posts/i5HimI73K" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Rust-based robotics framework HORUS for real-time performance</strong>: HORUS Framework is a production-grade robotics framework built in Rust, emphasizing real-time performance, memory safety, and a modular node-based architecture for efficient development. <a href="https://app.daily.dev/posts/tBD8atPlc" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Linux kernel 7.0 improves Rust and LTO builds</strong>: The upcoming Linux kernel 7.0 is set to enhance Rust and Link-Time Optimization (LTO) builds, with Google engineer Alice Ryhl’s work improving performance and code generation for Rust components. <a href="https://app.daily.dev/posts/eeFdKxuyc" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong><a href="http://OpenTelemetry.io" target="_blank" rel="noopener nofollow">OpenTelemetry.io</a> expands localization and ecosystem tools</strong>: <a href="http://OpenTelemetry.io" target="_blank" rel="noopener nofollow">OpenTelemetry.io</a> significantly expanded its localization to eight languages, launched an Ecosystem Explorer for easier library discovery, and is preparing for a homepage redesign and Collector documentation refactoring ahead of CNCF graduation. <a href="https://app.daily.dev/posts/rI2rLbbbQ" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>Node.js 22.22.0 LTS addresses security vulnerabilities</strong>: Node.js 22.22.0 LTS is a security release patching six CVEs, including fixes for TLSSocket error handling, futimes permissions, and unsafe buffer creation, ensuring a more robust runtime environment. <a href="https://app.daily.dev/posts/Zr0Dv9dwZ" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
<h2>Bullshit police</h2>
<ul>
<li><strong>AI coding tools: the productivity paradox</strong>: Apparently, AI coding tools are making developers ‘feel’ 20% faster, but academic research shows they actually take 19% longer to finish tasks, introduce 1.7x more code issues, and increase security flaws. It seems the ‘productivity boost’ is mostly a cognitive bias, and we’re just trading typing for debugging AI’s hallucinations. Who knew that blindly trusting a machine to write your code might lead to more work? <a href="https://app.daily.dev/feed-by-ids?id=02YtNeXqK&amp;id=fLWmEtnzQ&amp;id=zpPmuG4cG" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>The ‘AI verification bottleneck’ is the new ‘developer toil’</strong>: AI code generation is creating a ‘verification bottleneck,’ where developers spend more time reviewing unreliable AI-generated code than they save writing it. With 96% of developers not trusting AI code, and toil shifting from creation to correction, it seems AI is just moving the deck chairs on the Titanic of developer inefficiency. But hey, at least we’re generating more code, right? <a href="https://app.daily.dev/posts/SVMT3qR0j" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>AI is ‘killing’ open source business models, or is it just bad business?</strong>: Tailwind CSS laid off 75% of its engineers, blaming AI for an 80% revenue drop because LLMs are scraping their docs and users aren’t visiting their site. Their solution? Refuse an LLM-optimized documentation endpoint. It’s almost like relying on documentation traffic for revenue in the age of AI might be a flawed business model, not just an AI problem. Maybe open source projects should, you know, charge for their commercial use instead of just hoping for sponsorships? <a href="https://app.daily.dev/feed-by-ids?id=3KrG8AfuZ&amp;id=LLQ1zfubn&amp;id=f3fYMXuKZ&amp;id=hbFeNQ18o&amp;id=re8TItYuD&amp;id=mpCeVdjI4&amp;id=Ml47Y2Hd6" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>
