3 ms·
Another example from Rust community, without reading the article commenting that Rust is always correct without any bugs or error and programmer is stupid. Th
by dragonsh 6y ago
Another example from Rust community, without reading the article commenting that Rust is always correct without any bugs or error and programmer is stupid.
This attitude continuously drives me away from learning Rust, didn’t find such attitude in Haskell or Lisp community which really took computer science and art of programming forward unlike Rust, which is similar to other competing niche languages.
- arcticbull 6y agoTo be clear, that isn't what I meant, though I can't really edit my comment for clarity. Some things don't manifest the way you intend when converting from thoughts to text.
- doonesbury 6y agoSometimes I get the impression from rust advocate articles on HN that they are snobs. Not here; no way. This was well written, cheeky, thorough, and gave me a solid sneak peak at doing rust from a c/c++/go/python/Java background. The exacting standards of stopping data races at compile time is an exacting task. I think I followed most everything here, although I wondered if the crossbeam inclusion should be in language not library code ... But I don't know enough to press further. Solving problems in libraries not language probably is better. Rust is one of few if only languages I am aware of that hit hard on data safety without a gc. That'll make it quite different to the programmer.
- fasterthanlime 6y agoI'm happy you enjoyed the article! I seem to remember scoped threads were part of the standard library at some point, but they were eventually proved unsound and removed. I'm too lazy to go find a reference right now but it shouldn't be overly hard.