4 ms·
Why not Rust? I write both, Go feels incomplete, Rust is younger but is much more mature and filled in. I can write faster in Rust, its much like Python develop
by pard68 7y ago
Why not Rust? I write both, Go feels incomplete, Rust is younger but is much more mature and filled in. I can write faster in Rust, its much like Python development.
The mix of functional and imperative styles is odd, but not bad.
- nine_k 7y agoRust will eventually replace C++: it's useful in areas where performance matters and things cannot be dumbed down without much consequence. For a CRUD app server, its an overkill, though.
- w8rbt 7y agoIt may replace C++, but it will take decades to do so. The C and C++ ecosystem is gigantic and has been around for 30 to 40 years and will will be around for the next 100 years or more years IMHO.
- nine_k 7y agoReplace = new development is done in Rust, C++ development is for supporting (huge amounts of) existing C++ code. Even COBOL is not completely phased out by now, and runs in production, but it has been largely replaced by other languages.
- krapht 7y agoGarbage collection is a big productivity boost. That's why Java killed C++ to begin with in the enterprise space. You can't go backwards in that sense.
- kermitismyhero 7y agoIt's also easier on the learning curve. I've just gotten back into coding as a hobby after a two-decade-long gap. In that time every few years I've tried to pick up C, and always ended up bewildered and frustrated by garbage collection matters. Maybe with formal instruction I could have figured it out, but the learning curve as a weekend/evening hobbyist was like a vertical cliff. But in one month with Go, I've gone from "barely remembers his teenage QBasic days and dabbles in VBA at work" to "writing genuinely useful utilities with minimal time investment". I'm sure the language has limitations, but I've yet to run into any that are personal showstoppers.
- 0815test 7y agoIf there's one single reason why Java killed C++ in the enterprise space, it's memory safety. (Concurrency-readiness and WORA were also important features of course.) GC was not important, other than as a means to an end of course. What GC does in practice is open up new domains. There are object-management patterns that simply can't be written feasibly without something like a GC runtime under the hood. (Hence Greenspun's tenth rule of programming, of course.)
- slezyr 7y agoTry to write async code in Rust and you will see that Rust is the one that "incomplete".
- dfrage 7y agoI've read its story is inherently bad for working on graphs, which is a huge area for C++.