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.
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.
Thanks for the offer. I think we can still use volunteers for the day of. Send an email to hello@tokioconf.com
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
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-...
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!
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.
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!
Maybe `clone_handle()` is enough to disambiguate. Though, it isn't short.
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.
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.
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.
Heading up to Seattle for #rustconf. I am excited to see folks again.