A big Toasty release (async ORM for Rust)! The relation declaration API improved, added support for multi-step relations, update! macro with ops like increment / add / push, and support for Turso. github.com/tokio-rs/toa... .

This undercurrent within the #rustlang community (and others) has to stop. The attacks on people simply because they are using developer tools that make them productive is 100% out of line. I can respect the anti-LLM arguments, but let's agree to disagree, respect each other as humans, and move on.

I posted a bit about how I use LLM tools to boost productivity with a "complex Rust library" here: reddit.com/r/rust/comme.... If I motivate myself to do os, I will write some blog posts about my work flow.

I wrote a bit more about the release here: tokio.rs/blog/2026-05...

I think the crucial questions are a) is it *worse* than it was before, safety wise b) how will correctness trend over time starting from now.

Got my new hat in time for Rust Week. See you there.

Released Toasty v0.6 (ORM for Rust). Highlights include `#[deferred]` to avoid having to load all fields all the time, `.select(...)` specify exactly which fields you want, and support for `Vec` fields, which is the start towards full "document" modeling. github.com/tokio-rs/toa...

I don't have anything to add to the Bun/Rust rewrite, except I notice that the post hasn't been removed from /r/rust as "not 100% human written" yet. Interesting... (not at all holding a grudge 😅)

I can too, the answer is: YES! (kidding). Nicholas is great, so reach out to him if you need help with Rust.

Always fun when you come across someone who insists the only way to write reliable software is with a set of capabilities that happens to match what the Erlang VM provides. I guess everyone else is wrong.

What is the easiest way to set up automated AI agents (ideally Claude Code) that can react to GitHub events and submit PRs? For example, I want to auto-generate doc PRs for new functionality. GitHub Actions isn't ideal because CI doesn't trigger for PRs submitted from an action.

The most surprising thing to me is the Rust port compiles faster than the Zig repo. I thought Zig focused on compilation speed. Does someone know why this would be? xunroll.com/thread/20530...

Being old means I'm excited for Friday night because nobody else will be swimming laps at the pool, and it will be quiet.

Gotta book stuff for my upcoming trip to Europe. But first, I need to warm up my finger for the "accept all cookies" click marathon.

✨AI helps teams build faster. But sooner or later, something in production will behave unexpectedly -and that’s where visibility matters. On Netstack.FM Ep.37 we talk with Jess Izen and Russell Cohen from AWS on Dial9, a tool for seeing inside Rust and #Tokio apps. 🎧 netstack.fm#episode-37 #RustLang

Great talk, which led to this follow up issue and discussion. github.com/tokio-rs/tok...

So, it is cheaper to fly PDX -> AMS -> CPH -> AMS than to fly PDX -> AMS, even though the first option takes the exact same flight.

Using Tokio for CPU-Bound Tasks (Works Really Well) youtu.be/FeqRdDG1Y7g (has nothing to do with AI, just scheduling and Database plans)

The function coloring meme is one of those things that sounds true and is catchy if you don't think too hard about it. The reality is, there aren't two colors; there is a full gradient. Structure your code to best solve your problem.

What if maintainers for OSS projects said: "If you want security patches in a timely fashion, you **must** pay a subscription. Otherwise, we will just disclose the issue, then make the patch public in ~30 days". You would all lose your minds, but it also points out you *expect* work for free.

Every time an OSS maintainer adds a "funding" notice to their post-install, deletes their package, or doesn't merge a bug fix, and "the community" gets angry and calls it a bad action, that's the problem.

I don't have a totally coherent view on this, but having spent time in this space, OSS funding is just *weird*. Users treat popular projects like products, and how software gets done somewhat reinforces that (packaging, "the ecosystem", etc.). A very tiny # of people do (or even could!) make money.

I'm just going to say it, I really don't like the "how do we make OSS sustainable" framing. OSS is already sustainable. The only thing not sustainable is users expecting a free lunch (support, LTS, bug fixes, ...). As a user, you are responsible for your OSS usage. Fork/patch if you need to.

I'll be at #RustWeek next month. Always happy to chat Tokio, Toasty, Rust ORMs, or web apps in Rust. Say hi if you're around.

These days, I could probably build a web app to book airline travel faster than I can book a flight through corporate travel portals.

Is TokioConf about Rust or Ruby? 🤔

Sean Klein telling us about how FutureLock could ruin your weekend followed by Sarek Skotåm live demoing how Shuttle can catch it in tests. Did he put the live demo for his talk together during the break? 🤔

Day 2 of #tokioconf! Noah Kennedy is telling us about how Cloudflare switched from NGINX to a custom built proxy.

Congrats to the Tokio community for day 1 of #tokioconf! Ferris was pleased to get an invite (and these amazing stickers) 🦀 www.tokioconf.com For any TokioConf attendee that can't get enough #rustlang talks, we'd love to host you at #rustconf in Montréal this Sept. More info: rustconf.com

Glauber Costa sharing wisdom like “don’t rewrite the Linux kernel”

Pooja Kale sharing patterns for managing bounded concurrency with Tokio.

yo #tokioconf swing by and let's talk about deploying! or you can roast this gopher's novice Rust 😅 miren.dev/blog/gopher-...

I hear there’s a limited edition #tokioconf sticker 👀

hi portland! in town for tokioconf until Thursday ❤️ DM me if you're around and want to meet or hang out!

Time to fill some swag bags! See you next week. tokioconf.com.

LLMs are uncovering so many latent security issues. I suspect Rust-based software is going to look really good compared to JS/Go/Java services as this plays out. Looking forward to the analysis that will undoubtedly be written.

A very well reasoned article. I believe I am still in the center, leaning optimistic. I started using AI coding agents in July. They worked for tedious, but mechanical refactors. The tech has improved significantly since. I use coding agents for ~80% of Toasty work now: github.com/tokio-rs/toa...

Most developers use async runtimes. Few know how they came to be—or why they’re needed. On Netstack.FM 🎙️ Ep.34 (Remastered Ep.5), we revisit our conversation with Tokio creator @carllerche.com Timed with #TokioConf (Apr 20–22, 2026): www.tokioconf.com 🎧Listen at netstack.fm#episode-34 #rust #async

I am going to give a talk about why tokio.rs is a great choice for running CPU bound tasks in Database Query Egnines

So, I was playing with Gemini...

The @release-plz.dev crate is the tool I've been wanting for years! I've only added it to two crates so far, but it makes releasing crates so easy. I will be adding it to more over time for sure.

No more talking about rust-analyzer on /r/rust either. That is now "off topic": github.com/rust-lang/ru...

Apparently, if a crate is not 100% human written, it is off topic for /r/rust: reddit.com/r/rust/comme.... I have been working on Toasty for 3 years, 9 months with AI tools. I am quite proud of the code quality and stand by it. By their standard, the entire tokio-rs GitHub organization is now OT.

Toasty, an async ORM for Rust, is now on crates.io. This is the blog post that I promised: tokio.rs/blog/2026-04.... Happy to answer any questions here.

We are 3 weeks out from the first @tokioconf.com. Spoiler: This is the t-shirt! I just saw the design and had to share it. It is so exciting to see it all come together. You still have time to get tickets, but not much time! tokioconf.com.

A preview of the Toasty query! macro: github.com/tokio-rs/toa.... Some of it is already built: docs.rs/toasty/lates...

I finally published Toasty (async Rust ORM) crates! I’ll be writing about it soon (and why it took so long). github.com/tokio-rs/toa...

give 👏 clippy 👏 the 👏 call 👏 graph

Wow, dial9 (by Russel Cohen) looks killer. It's a flight recorder for Tokio that gathers runtime metrics and renders them. Service teams at AWS have already had success with it. Blog post: tokio.rs/blog/2026-03...

We're setting aside 20 free TokioConf tickets for contributors and open source maintainers. If you've submitted a PR to any tokio-rs, hyperium, or tower-rs repo, that's you. Know someone who qualifies? Send them our way! tokio.rs/blog/2026-03...