I hate Tokio. This is a piece of shit that just makes developers angry instead of getting things done. This is what made me hate Rust. Struggling to make a Hello World, yes, after that Tokio reform, is not normal. I would never consider Rust ever again to write servers.
-
-
Replying to @jedisct1
What's are you struggling with in particular? I feel like the Tokio devs would very much like to hear feedback if you're struggling with anything!
3 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
I would give anything to have garbage collection (yes) instead of having to use Rc, Arc, RefCell and clone() and boxes everywhere when using futures. That’s annoying, counterproductive and ugly as fuck.
1 reply 0 retweets 1 like -
Replying to @jedisct1
Ah yeah, that makes sense! From my understanding this will all get a lot better once the async/await stuff lands. Probably no more boxing of stuff for most cases! - but that's still a few months out last I heard. Sorry this isn't working out alright for you :(
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
I’d love to have just a `spawn()` function that schedules on the current thread, a `spawn_send()` that balances across multiple threads, and nothing else. Not having to worry about executors, tasks, threads, reactors and whatnot. That would make the system way more accessible.
1 reply 0 retweets 1 like -
-
Replying to @yoshuawuyts
And speaking of breakage, crates using tokio_core are incompatible tokio (not core). Because you can’t give a tokio::reactor::Handle to something expecting a tokio_core::reactor::Handle. This is as messy as Node in the early days.
1 reply 0 retweets 1 like -
Replying to @jedisct1 @yoshuawuyts
Seriously, Rust is an amazing language, but Tokio ruined it.
1 reply 0 retweets 0 likes
yeah, I'm crossing my fingers this will improve - I feel like a lot of people care enough about this; so just like Rust turned out alright, hopefully Tokio will too! Just needs... time? Personally I'm going to stay away from Rust async io for a little bit longer, haha.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.