3 ms·
Sparing few allocations at the risk of making the language inconsistent is an extremely bad way of building a programming language. If you write async code, rul
by nbittich 2y ago
Sparing few allocations at the risk of making the language inconsistent is an extremely bad way of building a programming language. If you write async code, rules are not the same than non async code. I am using rust for 4 years, I think I have a good enough level with it and thank God I kept my objectivity. Btw this is at the first page of the rust website, not "c++ replacement" : A language empowering everyone to build reliable and efficient software.
- spacechild1 2y ago> Btw this is at the first page of the rust website, not "c++ replacement" They wish :) Why should anyone - apart from aesthetic preferences - fight the borrow checker and deal with long compile times when they can just use a language with GC? It just doesn't make sense to me from a technical standpoint. You reach for Rust or C++ when you can't use C#, Go or Java. > If you write async code, rules are not the same than non async code. The thing is: Rust is (also) catering to people who want to write async code on embedded devices.