Carl Lerche

Carl Lerche

@carllerche.com

I do stuff, I say stuff. It's serious business.

394 followers66 following109 posts

Carl Lerche reposted

Replying to @carllerche.com

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

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 Wenger@fasterthanli.me

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.

This is also why I'm being so open with my use of LLMs in the public #rustlang spheres and I will keep doing so. I have the ability (built up my thick skin over the years) and reputation to disregard the attackers, but many others don't.

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

github.comgithub.com
Carl Lerche@carllerche.com

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

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

View full thread

I will say that I am glad Bun is not a project I have to maintain though, I wouldn't have had the guts to switch languages so quickly.

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

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

I do know that long lived forks are a recipe for failure and if I had to port a large project from one language to another, I would also try to make the port as mechanical as possible, then iterate from there.

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

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.

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.

Carl Lerche reposted

✨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.fmNetstack.FM® — A Podcast About Networking and RustInterviews, monologues, and deep dives into Rust and modern networking systems.

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.

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

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.

This might be something that happens w/ the EU cyber resilience act. Granted, I just skimmed the content, but I am excited to see what happens.

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

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.

View full thread

If you want support, pay for it. And no, donating $20/mo, is not the answer. It costs more to take an OSS project and turn it into a product that businesses can depend on.

It's fine to highlight technical issues and crowdsource a knowledge base on the state of each dependency. But remember: OSS is published WITHOUT WARRANTY.

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

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.

The problem is that we, "the community," have an expectation from devs who make their code open. And no, it's not on them to put disclaimers in their README.

Carl Lerche reposted

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

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.

This is not to say we shouldn't explore ways to crowd source bug fixing, support, etc... but that is all bonus and not a requirement to be "sustainable".

That said, based on my quick read of the information out there on the Cyber Resilience Act, I think it might end up being decent. It clearly places the onus on the companies building products with OSS.

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

Carl Lerche reposted

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? 🤔