Three years ago, trying to use Rust for web apps was crazy talk. Today is very different than three years ago. Announcing Topcoat, a batteries-included Rust framework for building reactive web applications: tokio.rs/blog/2026-07...

I REALLY like that I have server controlled reactivity without the need to build wasm. People will underestimate what an amazing thing that is.

👀👀👀 github.com/tokio-rs/top... #rust-lang

GitHub - tokio-rs/topcoat: A batteries-included framework for building web apps

A batteries-included framework for building web apps - tokio-rs/topcoat

github.com

About a month ago I gave a talk at Tokioconf on what shared-nothing and work-stealing are, and how migrating our stack from nginx+lua to rust and tokio massively improved our performance ...because of work-stealing! check it out the recording here: www.youtube.com/watch?v=6QN3...

TokioConf 2026 - From NGINX to Tokio: Lessons from rewriting a 55 million RPS system by Noah Kennedy

YouTube video by TokioConf

youtube.com

The TokioConf 2026 talks are now available on YouTube: youtube.com/playlist?lis.... Also, TokioConf 2027 will be April 26 & 27, 2027 in Portland, OR. Save the date!

TokioConf 2026 - YouTube

Organized by the Tokio team to facilitate networking and knowledge exchange among engineers tackling similar challenges in Rust. A dedicated conference for d...

youtube.com

my futurelock talk from #tokioconf is up! check it out, enjoy the story of a nightmare bug we saw at @oxide.computer

TokioConf 2026 - Futurelock And You by Sean Klein

YouTube video by TokioConf

youtube.com

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... .

Release Toasty v0.7.0 · tokio-rs/toasty

Highlights Relations are now plain fields, with eager loading by default. The HasMany, HasOne, and BelongsTo wrapper types are gone. A relation field is just its target type, and whether you wrap i...

github.com

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.

amos@fasterthanli.me · 3mo ago

prepping for rustweek, bracing to cross paths with all the people who decided to call me a booster/traitor/fascist for using LLMs, the people who blocked me without saying anything, the people who maintain lists of who to shun. a lot has happened in a year that I'm not done grieving about.

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.

carllerche's comment on "Toasty v0.6 (ORM) released. What's is new?"

Explore this conversation and more from the rust community

reddit.com

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

Carl Lerche@carllerche.com · 3mo ago

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 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.

rain 🌦️@sunshowers.io · 3mo ago

#30719 is a bit terrifying — they didn't even vibecode a CI check for Miri? Really concerned this is going to seriously harm Rust's reputation github.com/oven-sh/bun/...

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...

GitHub - tokio-rs/toasty: An async ORM for Rust

An async ORM for Rust. Contribute to tokio-rs/toasty development by creating an account on GitHub.

github.com

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.

nrc@ncameron.org · 3mo ago

I can help you assess if Rust is a good fit for your team or company, guide your Rust adoption, and help develop a Rust strategy. I have availability pretty much immediately, get in touch for a free chat: nrc@ncameron.org, or www.ncameron.org for more info.

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...

Xunroll - Free Twitter Thread Reader & PDF Converter

Read, unroll and convert Twitter/X.com threads to PDF online without an account. Free thread reader tool.

xunroll.com

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

Netstack.FM® — A Podcast About Networking and Rust

Interviews, monologues, and deep dives into Rust and modern networking systems.

netstack.fm

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

Improved experience using Tokio for both CPU-bound work and I/O work on the same machine · Issue #8085 · tokio-rs/tokio

Is your feature request related to a problem? Please describe. Thanks First of all, Tokio is awesome, and shout out to my peeps @carllerche and @Darksonn for their amazing work on this crate. We us...

github.com

Andrew Lamb@andrewlamb1111.bsky.social · 3mo ago

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

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)

Using Tokio for CPU-Bound Tasks (Works Really Well) May 2026

YouTube video by Andrew Lamb

youtu.be

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.

Carl Lerche@carllerche.com · 3mo ago

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.

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.

Carl Lerche@carllerche.com · 3mo ago

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 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.

Carl Lerche@carllerche.com · 3mo ago

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'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.