News for hackers. Stuff that matters.
Re:Why has CPU frequency ceased to grow? (2014) by gilrain on Wednesday February 21, 2018 @11:05AM (#16430409)
Try it out and write the critique, then. The posts are positive because Rust is genuinely achieving rapid progress and stability... but certainly not without flaws.

I've experienced plenty of frustration, albeit outweighed by the massive benefits for my use case. And there are whole problem domains to which it's just not suited. I see these mentioned pretty frequently.

Re:Why has CPU frequency ceased to grow? (2014) by Thaxll on Wednesday February 21, 2018 @11:45AM (#16430761)
For once there is no consensus how to do parallelism an concurrency in Rust since none of the library are matures.
Re:Why has CPU frequency ceased to grow? (2014) by kibwen on Wednesday February 21, 2018 @04:07PM (#16432982)
> none of the library are matures.

Rayon, the Rust library getting most of the discussion in this thread, is now 1.0: https://github.com/rayon-rs/rayon/blob/master/RELEASES.md .

Re:Why has CPU frequency ceased to grow? (2014) by coldtea on Wednesday February 21, 2018 @12:14PM (#16431007)
Don't most people opt for something called Tokyo? I don't do Rust much, but even I have heard of it by now...
Re:Why has CPU frequency ceased to grow? (2014) by steveklabnik on Wednesday February 21, 2018 @12:25PM (#16431108)
Tokio for IO concurrency, Rayon for data parallelism.
Re:Why has CPU frequency ceased to grow? (2014) by Bitcoin_McPonzi on Wednesday February 21, 2018 @01:17PM (#16431576)
Exactly! Rust doesn't solve any parallelism problems. It's no better than established languages like C# or F#, and probably worse.
Re:Why has CPU frequency ceased to grow? (2014) by vvanders on Wednesday February 21, 2018 @04:02PM (#16432953)
I'd consider handling data races gracefully a pretty large step forward in doing parallel data computation.