L 0 K 1 on Nostr: The borrow checker is way too complicated. Give me a well tuned mark and sweep GC any ...
The borrow checker is way too complicated. Give me a well tuned mark and sweep GC any day. Latency of concurrent processing matters a lot more on a system with heavy load and Rust has zero to add to the field regarding this matter.
Rust is just a fad language, just like C++ was a fad language back in 1992. It has precisely one feature distinct from C++, and cargo is basically a carbon copy of Go's build system with macros added, so, sorry, it doesn't count.
Sure, it saves compilation time, most of the time, but it's still at least 100x faster to compile the same app in Go, versus Rust, from scratch.
I doubt the trade-off of security and safety of the borrow checker really stacks up against the speed of C execution and hand-optimisation.
Variants, objects and templates are very expensive features to compile. Programmers abuse these tools all the time, leading to the endless, predictable bloat of lower throughput and higher resource consumption.
Rust does nothing towards teaching programmers to write simple, clean code. It just gives you a very hard to learn way of making an extra few fractions of a percentage of safety for maybe 10% throughput but gives you no reduction in latency and takes about 3 months for average programmers to master this most fundamental feature.
And like all macro-using, preprocessor using languages, it gives so much expressivity that learning how to do anything with the language starts with a long review of the myriad of options, instead of a solution that is precisely the fit and most concise and performant.
Rust is just a fad language, just like C++ was a fad language back in 1992. It has precisely one feature distinct from C++, and cargo is basically a carbon copy of Go's build system with macros added, so, sorry, it doesn't count.
Sure, it saves compilation time, most of the time, but it's still at least 100x faster to compile the same app in Go, versus Rust, from scratch.
I doubt the trade-off of security and safety of the borrow checker really stacks up against the speed of C execution and hand-optimisation.
Variants, objects and templates are very expensive features to compile. Programmers abuse these tools all the time, leading to the endless, predictable bloat of lower throughput and higher resource consumption.
Rust does nothing towards teaching programmers to write simple, clean code. It just gives you a very hard to learn way of making an extra few fractions of a percentage of safety for maybe 10% throughput but gives you no reduction in latency and takes about 3 months for average programmers to master this most fundamental feature.
And like all macro-using, preprocessor using languages, it gives so much expressivity that learning how to do anything with the language starts with a long review of the myriad of options, instead of a solution that is precisely the fit and most concise and performant.