2 ms·
It's hard to optimize for readability, performance, and safety. Rust chose to go with performance and safety. In the future, maybe we can have a language that g
by ModernMech 4y ago
It's hard to optimize for readability, performance, and safety. Rust chose to go with performance and safety. In the future, maybe we can have a language that gives all three but not today.
- eternalban 4y agoSame thing that happened with type declarations will need to happen to semantic intent: inference.
- verdagon 4y agoShameless relevant plug: that's the exact goal of Vale! [0] It turns out, when one removes the borrow checker, they get something that's much more readable, because a lot of Rust's complexity was added to help support the borrow checker. Ironically, we can then add back in a different, easier form of borrow checking to get the speed benefits. [0] https://vale.dev/ https://vale.dev/
- vrfvr 4y ago> Rust is also very difficult. It's as complex as C++, and throws it all at the programmer at once. I thin Rust isnt nearly as complex
- IshKebab 4y agoIt definitely is. You've probably just had more time to discover the complexity of C++ (and read about it, since it's actually specified). Of course Rust's complexity is much less dangerous because if you forget some obscure rules you get a compile error instead of UB (in safe Rust at least).
- IshKebab 4y agoVale sounds very promising (I'm also closely following Koka). But one thing I've found is that Rust's ownership/borrowing model does more than just eliminate GC. It also seems to encourage good program structure that is less prone to logic bugs. I don't have solid evidence for that - more of a feeling. But I wonder if switching to reference counting would lose that. Anyway, just an observation.
- NoGravitas 4y agoVale looks exciting. Thanks for the link.
- quirino 4y agoIt's refreshing to see such a simple, good-looking and informative website. Also incredibly fast! Please keep it that way.