3 ms·

In all this time, maestro Andrei Alexandrescu was right when he said Rust feels like it "skipped leg day" when it comes to concurrency and metaprogramming capab

In all this time, maestro Andrei Alexandrescu was right when he said Rust feels like it "skipped leg day" when it comes to concurrency and metaprogramming capabilities. Tim Sweeney was complaining about similar things, saying about Rust that is one step forward, one step backward. These problems will be evident at a later time, when it will be already too late. I will continue experimenting with Rust, but Zig seems to have some great things going on, especially the colourless functions and the comptime thingy. Its safety story does not dissapoint also, even if it is not at Rust's level of guarantees.

aw1621107 6y ago
In case anyone else was interested in the original sources for the quotes: > Andrei Alexandrescu was right when he said Rust feels like it "skipped leg day" when it comes to concurrency and metaprogramming capabilities. https://archive.is/hbBte https://archive.is/hbBte (the original answer appears to have been deleted [0]) > Tim Sweeney was complaining about similar things, saying about Rust that is one step forward, two steps backward. https://twitter.com/timsweeneyepic/status/1213814236184485889 https://twitter.com/timsweeneyepic/status/121381423618448588... (He said "Kind of one step backward and one step forward", but close enough) [0]: https://www.quora.com/Which-language-has-the-brightest-future-in-replacement-of-C-between-D-Go-and-Rust-And-Why/answer/Andrei-Alexandrescu https://www.quora.com/Which-language-has-the-brightest-futur...
- johnnycerberus 6y ago
  Thanks for the references, indeed, Tim said one step forward, one backward, my bad. He posted long time ago.
jedisct1 6y ago
And Zap (scheduler for Zig) is already faster than Tokio. Zig and other recent languages have been invented after Rust and Go, so they could learn from them, while Rust had to experiment a lot in order to combine async with borrow checking. So, yes, the async situation in Rust is very awkward, and doing something beyond a Ping server is more complicated than it could be. But that’s what it takes to be a pioneer.
- winter_squirrel 6y ago
  Are there any benchmarks / links for zap? I tried searching and didn't find much
- the_duke 6y ago
  > And Zap (scheduler for Zig) is already faster than Tokio. I'm not necessarily doubtful, tokio isn't the fastest implementation of a runtime. But can you point to a non-trivial benchmark that shows this? Performance claims should always come with a verifiable benchmark.
  - jedisct1 6y ago
    Check out @kingprotty's Twitter posts and Zig Show presentations.
pcwalton 6y ago
D and Zig have dynamically typed generics (templates/"comptime thingy"), while Rust has statically typed generics. A lot of people confuse this for Rust having less powerful generics. It's simply a different approach: the dynamic vs. static types distinction, at the type level instead of the value level.

aw1621107 6y ago

In case anyone else was interested in the original sources for the quotes: > Andrei Alexandrescu was right when he said Rust feels like it "skipped leg day" when it comes to concurrency and metaprogramming capabilities. https://archive.is/hbBte https://archive.is/hbBte (the original answer appears to have been deleted [0]) > Tim Sweeney was complaining about similar things, saying about Rust that is one step forward, two steps backward. https://twitter.com/timsweeneyepic/status/1213814236184485889 https://twitter.com/timsweeneyepic/status/121381423618448588... (He said "Kind of one step backward and one step forward", but close enough) [0]: https://www.quora.com/Which-language-has-the-brightest-future-in-replacement-of-C-between-D-Go-and-Rust-And-Why/answer/Andrei-Alexandrescu https://www.quora.com/Which-language-has-the-brightest-futur...

johnnycerberus 6y ago
Thanks for the references, indeed, Tim said one step forward, one backward, my bad. He posted long time ago.

jedisct1 6y ago

And Zap (scheduler for Zig) is already faster than Tokio. Zig and other recent languages have been invented after Rust and Go, so they could learn from them, while Rust had to experiment a lot in order to combine async with borrow checking. So, yes, the async situation in Rust is very awkward, and doing something beyond a Ping server is more complicated than it could be. But that’s what it takes to be a pioneer.

winter_squirrel 6y ago
Are there any benchmarks / links for zap? I tried searching and didn't find much
the_duke 6y ago
> And Zap (scheduler for Zig) is already faster than Tokio. I'm not necessarily doubtful, tokio isn't the fastest implementation of a runtime. But can you point to a non-trivial benchmark that shows this? Performance claims should always come with a verifiable benchmark.
- jedisct1 6y ago
  Check out @kingprotty's Twitter posts and Zig Show presentations.

pcwalton 6y ago

D and Zig have dynamically typed generics (templates/"comptime thingy"), while Rust has statically typed generics. A lot of people confuse this for Rust having less powerful generics. It's simply a different approach: the dynamic vs. static types distinction, at the type level instead of the value level.