Re:Rust can be difficult to learn and frustrating, but it's ...
by kenhwang on Monday October 22, 2018 @07:21PM
(#18279447)
I eventually got something working, and it was stupid stupid fast, but it definitely took a lot longer to write than I would've liked.
Just waiting for the features and APIs to finalize and async/await for the ergonomics improvements. I believe in it's potential, but I'm in no hurry to use it again in it's current state.
Re:Rust can be difficult to learn and frustrating, but it's ...
by pimeys on Tuesday October 23, 2018 @06:54AM
(#18282299)
Didn't mean though I think the current situation is that bad. What you get already is a type safe way to build async programs where the runtime is separated from the logic. I remember switching from a single threaded event loop into a work-stealing threadpool by just changing one line of code. It's very explicit and nice.
But for newcomers, be careful with references when using futures and be smart how you use the combinators. The errors can be tough and this is the only place in Rust ecosystem where they don't really help at all sometimes.