January

via Rust Weekly 🦀 (@rust_discussions@mastodon.social): Why Rust in Production?

Matthias Endler talks through several arguments for and against using Rust in production based on his experience consulting with many firms large and small.

Ryan Trimble shares a handful of VS Code plugins he’s used so long he forgot they weren’t built-in — Markdown All in One (paste a URL over selected text to make a Markdown link), Better Comments for highlighted TODO/alert annotations, and Peacock for color-coding windows per workspace. Handy if you do a lot of Markdown authoring or juggle many projects at once.

via Rust Weekly 🦀 (@rust_discussions@mastodon.social): My Best and Worst Deadlock in Rust

Michael Snoyman walks through building a subtle Rust deadlock step by step, using an RwLock-guarded struct and a seemingly innocent read-then-write pattern. It’s the “worst” deadlock because it hides in plain sight, and the “best” because the tooling pointed straight at the culprit. Worth reading even if you think you know Rust’s concurrency rules.

via Andrew Lokenauth (@FluentInFinance@mastodon.social): The wealthy avoid taxes using the “Buy-Borrow-Die” strategy:

Andrew Lokenauth walks through the “Buy-Borrow-Die” strategy: the wealthy hold appreciating assets, borrow against them at low rates instead of selling (avoiding capital gains), and pass the assets on with a stepped-up basis so the gains are never taxed. A concise explanation of a tax loophole that’s hiding in plain sight.

A browser-based editor for building realistic US highway guide signs — panels, shields, control cities, arrows, and all — with the ability to save the result as an image. Ooh, this could be dangerous!

Luca Palmieri fills a real gap in the Rust adoption literature: not how to convince your org to try Rust, but what to do once you’ve decided. His advice to not hire Rust specialists for your first project — and instead assess and upskill the team you already have — rings true, as does the warning about stranding a team of frustrated Rust experts if the bet doesn’t pan out.

Dan Moren drops Feedly and moves his RSS subscriptions into Reeder’s own iCloud-synced feed list, cutting out the sync service entirely. The bigger point: RSS and OPML remain one of the few places where moving your data between apps and services takes about a minute — a portability standard the rest of the web could learn from.

Prossimo’s benchmarking work on Rustls shows the Rust TLS implementation already beating OpenSSL 3.2 in several scenarios, with automated per-PR performance feedback to catch regressions. A nice demonstration that memory safety doesn’t have to come at the cost of performance — historically the main argument for staying with C.

via Axel Rauschmayer (@rauschma@fosstodon.org): Two projects that sync in-browser SQLite databases with servers:

SQLSync is a collaborative, offline-first wrapper around SQLite that syncs web application state between users, devices, and the edge. Written in Rust and compiled to WASM, it brings reactive query subscriptions and automatic conflict resolution to local-first apps without requiring you to hand-roll a sync layer.

via Jan (@janpio@hachyderm.io): @scouten@ericscouten.social we have been trying https://codspeed.io/ for that use case. Works decently. Check github/prisma/prisma-engines PRs for examples.

CodSpeed runs benchmarks as part of CI and flags performance regressions directly in the pull request, using instrumentation rather than wall-clock timing so results aren’t drowned out by noisy shared runners. It supports Rust, Python, Node, and Go, and several open source projects use it to keep an eye on performance drift over time.

Terry White chronicles replacing his aging whole-house Bose SoundTouch setup with Sonos, after years of watching a discontinued product line slowly rot — half-baked AirPlay 2 support, speakers dropping offline, and no hope of fixes. A good reminder that with connected hardware, you’re buying the vendor’s software commitment as much as the speakers themselves.