ehm... no? A perfect set of restrictions would make it impossible for you to make mistakes but allow all code that is correct resource-wise. Rust's ownership model does not, and relaxing those rules is one of the biggest goals of rust maintainers.
What in the hell makes it bad? A unified package ecosystem? A de facto toolchain? Helpful borrow checking? The hugs you get from the compiler error messages? Benchmarks that make it competitive with C? Playing well with python? Not having to generate needlessly redundant header files? Amazingly powerful macro system? Much smarter handling of `null`? A de facto manual and excellent tutorials?
I mean, I'm a humble mechanical engineer and barely know what I'm doing in software development, but I thought all these things were fun to learn about and offered a powerful way to write code that is way faster, more robust, and more easily maintainable than the MATLAB environment in which I cut my teeth on programming.
,... L? Y. Bueno.,
V J. 55
17 Comments
entropySapiens@reddit
Antervis@reddit
entropySapiens@reddit
Antervis@reddit
entropySapiens@reddit
Antervis@reddit
ibo5534@reddit
entropySapiens@reddit
LanceMain_No69@reddit
Nal_Neel@reddit
randel_@reddit
zoqfotpik@reddit
P1P3_L0K0@reddit
zan9823@reddit
P1P3_L0K0@reddit
AltruisticDetail6266@reddit
PennyFromMyAnus@reddit