4 ms·
Thanks for the the tutorial! Rust seems a bit too complex to me. Like a C++ on steroid that wants to do and be everything. Nothing wrong with that but not my cu
by patrickaljord 13y ago
Thanks for the the tutorial! Rust seems a bit too complex to me. Like a C++ on steroid that wants to do and be everything. Nothing wrong with that but not my cup of tea. I'd rather stick to C if I need tight memory management, it is way simpler and straight forward. And if I need concurrency, I'll stick to Golang (or erlang). Really, it's such a pleasure to read some golang after reading this 30 minutes of Rust. Anyway, just my opinion.
- duaneb 13y agoI would argue that rust is both simpler and more consistent than either C or C++. No preprocessor, no pre/post increment, a real type system (instead of templates)—there's just not the mountain of undefined parts of the language that tends to be a large problem. Scala, in spite of being on a VM, is far closer to C++ IMHO in terms of attitude. I actually find golang harder to read without parametric types (sans built-in slices and maps).
- steveklabnik 13y ago> I'd rather stick to C if I need tight memory management, it is way simpler and straight forward. Well, if you don't want your C to segfault, you have to understand these concepts anyway, they're just implicit to the language. C's memory management may be simple, but it's surely not easy.
- pcwalton 13y ago> Rust seems a bit too complex to me. Like a C++ on steroid that wants to do and be everything. No, that's explicitly not a goal. The goal is to enable zero-cost abstractions and memory safety. Everything here is in service of that goal. > I'd rather stick to C if I need tight memory management, it is way simpler and straight forward. The problem is that the "simple and straightforward" model of C leads to a lot of very not-simple-and-straightforward time in front of Valgrind to get the program to work, or worse, to fix security vulnerabilities.
- pjmlp 13y ago> C if I need tight memory management, it is way simpler and straight forward If you work alone yes. Good luck on a 50+ developer team size, with high atrition rates.
- masklinn 13y ago> Like a C++ on steroid Rust most definitely isn't "like a C++ on steroid" from a complexity standpoint. It tries (and — I think — mostly succeed) to be a significantly simpler and more coherent language. It does make things which are implicit in C or C++ (e.g. ownership) explicit. That's a good thing, you need to know your ownership in C or C++, the language just doesn't help you much.
- azth 13y ago> Really, it's such a pleasure to read some golang after reading this 30 minutes of Rust. Incidentally, I find reading Go to be much more verbose and even heaver cognitively compared to reading Rust code.