I haven't received my author's copies yet, but Amazon just notified me that the print edition of Advanced Hands on Rust is now available. a.co/d/fKDDReZ You can also buy the ebook from Pragprog right now, 50% off with the coupon code "save 50" #rust

Can AI build a production-ready REST API in Rust in just 7 minutes? 🦀🤖 In Episode 3, @herberticus uses OpenCode and a detailed ~100-line prompt to build a tested, Dockerized bookstore service. → Multi-crate architecture → Strongly typed IDs → Shared authentication middleware → Idempotent database migrations Better instructions. Better architecture. More maintainable code. 🎥 Watch: piped.video/EdZ4wduM2qI

See #WISPPlanner: wispplanner.com/ and #LibreQoS v3 live at #WISPAPALOOZA by @WISPAnews - Booth 108! ​We’ll also be demonstrating LibreQoS v3, with a new architecture rewritten around #DPDK for substantially higher performance. #bufferbloat #latency #jitter #QoE #ISP

We just released Polars 2.0. It removed many of our legacy decisions makes the streaming engine our default and promotes SQL to a first class citizen within Polars. It comes with initial out-of-core (spill to disk) support, a new Map data type and a lot of performance improvements. In fact, we think Polars is now one of the fastest analytical SQL engines on a single node. See benchmarks in the post: pola.rs/posts/release-polars…

Can you just build things with AI agents? 🕹️🦀 In Episode 2, @herberticus puts it to the test by building Pong in Rust with two different approaches: → 1-line prompt vs. 19-line engineered prompt → Macroquad vs. Bevy → Debugging with AI agents → Code quality and modularity → The “genie problem” with ambiguous prompts AI can write the code. Engineering knowledge still shapes the result. 🎥 Watch: piped.video/1qb6xrePL8I

As much as I hate quoting DHH, the results only surprised me in that Go should have done a little better. Presumably he didn't read the code for any of the languages. Rust is (almost) always a good performance choice.

Such a great confidence!

Gotta love it when you find a tiny bug (in some code that has gone from Fortran to C, C to C++ and then C++ to Rust, bug in the C port and copied faithfully!) that has apparently been in production for 12 years - and nobody noticed.

I'm still looking forward to teaching Rust workshops at IEEE-CARS, but I accidentally quote tweeted a post from a year ago. So instead, here's this year's schedule! ieee-cars.org/program/schedu…

Always fun when you have some db test fixtures as part of a project, and somehow the "clean up afterwards" gets gunked... just reclaimed 80gb of completely pointless Postgres databases. :-/

.@LibreQoS have been nominated in 2 categories for @WISPAnews - Wireless Internet Service Providers Association Awards: surveymonkey.com/r/SVMHFBQ “Manufacturer of the Year" and "Triumph Award” - you can vote for us! #WISPs #bufferbloat #latency #jitter #broadband #QoE #ISP

Pretty happy with how this came out in wisp planner. Line of sight from towers, adjust the height above the surface of potential receivers for smooth updates. Probably need to work on the colour a little more. (Rust back-end, binary websockets and Rust/WASM in the browser)

Rust's Allocator API is now stabilized, it'll drop in Rust 1.100!

“The internet is a giant copying machine”: Interview with @VintonGCerf thebulletin.org/premium/2026… @DanDrollette via @BulletinAtomic #VintCerf #Internet #LLMs #AI #Google #ARPANET #DARPA

I'm generally supportive of "rewrite in Rust", but I do think you should learn a bit of Rust first. (Same for other languages!)

You can vote for #LibreQoS at @WISPAnews Awards! #bufferbloat #latency #jitter #broadband #ISP #WISP #FISP #LowLatency #BandwidthIsALIE #DaveTaht #OpenSource #WISPA #WISPs #Internet #FOSS #FLOSS #QoE #QoS #QualityOfExperience

#LibreQoS have been nominated in 2 categories for @WISPAnews - Wireless Internet Service Providers Association Awards: surveymonkey.com/r/SVMHFBQ “Manufacturer of the Year" and "Triumph Award” - you can vote for us! #WISPs #bufferbloat #latency #jitter #broadband #QoE #ISP #FISP

Is there a term for "I made an LLM call, and should have written an IF statement"? (or a simple fuzzy manifold check for that matter) Seeing this in too many workflows, and I don't know a name for the anti-pattern!

Rust + AI agents? There’s a lot more to the combination than speed. In Episode 1 of our Rust for Agentic Development guide, @herberticus breaks down: → Native performance + lower resource usage → Memory safety → Why Rust works well with AI-generated code → Compiler-enforced guardrails → Enterprise AI considerations 🎥 Watch: piped.video/H7gFuy6Xji4

Went to drive my little one to school, and found that the city had helpfully put traffic cones on everyone's driveway. Drove her to school anyway, and now I'm wondering when I can get back in! They apparently dug up the whole road surface in the time it took me to get to school!

If you work with Tokio, this is a must read: "Principles for fast Tokio applications" dial9-rs.github.io/blog/prin…