Carl Lerche's Avatar

Carl Lerche

@carllerche.com

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

121
Followers
46
Following
10
Posts
28.04.2023
Joined
Posts Following

Latest posts by Carl Lerche @carllerche.com

Same old story: big company takes over, talented employees move on, corporate pushes new features and deadlines, Jr devs w/ no ability to push back ship as fast as possible, sacrificing quality. Rinse and repeat.

05.03.2026 19:06 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Thanks for the offer. I think we can still use volunteers for the day of. Send an email to hello@tokioconf.com

27.02.2026 17:19 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Preview
High Leverage | Ep. #6, Async Runtime For Rust with Carl Lerche of Tokio | Heavybit On episode 6 of High Leverage, Joe Ruscio speaks with Carl Lerche of Tokio about building high-performance systems in Rust.

I went on a podcast to talk about Rust, async programming, and Tokio. Happy to answer any questions or you can just tell me I'm wrong.

hubs.ly/Q040QsRg0

04.02.2026 18:06 πŸ‘ 2 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0
Preview
Meet the Speakers β€” TokioConf 2026 Discover the speakers behind TokioConf 2026. From core maintainers to community leaders, our lineup shares real-world experience and insights.

We’re excited to share the complete list of speakers joining us at TokioConf 2026 covering performance tricks, architecture patterns, and more.

See all our speakers: www.tokioconf.com/speakers
(Schedule coming soon)

Tickets are on sale: www.eventbrite.com/e/tokioconf-...

09.01.2026 22:11 πŸ‘ 12 πŸ” 4 πŸ’¬ 0 πŸ“Œ 1

Buy your ticket now! If we sell out soon, we might be able to expand to accommodate more, but only if we have enough time to do so!

08.01.2026 23:49 πŸ‘ 2 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0
Preview
TokioConf 2026 | Be a Part of Tokio's Official Conference! Join 300+ developers at the inaugural TokioConf 2026 to exchange ideas, learn from one another, and explore the future of async Rust. Hosted by the Tokio Project

The #tokioconf speakers and talks just got posted: www.tokioconf.com Ticket sales are open! Since it is our first conference, it is hard to estimate how many people will come. We're starting conservative, only 200 tickets right now.

08.01.2026 23:48 πŸ‘ 10 πŸ” 4 πŸ’¬ 2 πŸ“Œ 0
I'm speaking at TokioConf 2026 about "Futurelock and You"

I'm speaking at TokioConf 2026 about "Futurelock and You"

For Rust people interested in async code at TokioConf, I'll see y'all in April!

05.01.2026 17:56 πŸ‘ 28 πŸ” 6 πŸ’¬ 0 πŸ“Œ 0

Maybe `clone_handle()` is enough to disambiguate. Though, it isn't short.

15.10.2025 15:13 πŸ‘ 2 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

You may not have a problem with it, but it is something I see *many* software engineers working with Rust have problems with. Consider the type being cloned may not be Vec or Arc but some custom type. Being able to understand the execution behavior of code in a localized context is pretty important.

15.10.2025 15:12 πŸ‘ 2 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

I’ve been of the belief that using clone as the main api for incrementing ref counts is not great beyond the boilerplate of cloning: it hides the complexity of the op when looking at some code in isolation. The good news is that this can be fixed in a backwards compatible way.

07.10.2025 17:46 πŸ‘ 5 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

I do agree that there is a concept of Handle already across the rust ecosystem and nailing down a trait to represent that is good. Not sure if Handle is idiomatic as rust traits with one method tend to be verbs. It would also cause some clash with existing types names Handle. Minor issues though.

07.10.2025 17:42 πŸ‘ 16 πŸ” 0 πŸ’¬ 3 πŸ“Œ 0

Heading up to Seattle for #rustconf. I am excited to see folks again.

02.09.2025 16:57 πŸ‘ 7 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0