4 ms·
Hey, at least they didn't pick "move fast and break things" as a core principle. They're doing better than C/C++.
by zozbot234 5y ago
Hey, at least they didn't pick "move fast and break things" as a core principle. They're doing better than C/C++.
- ipaddr 5y agoWhen you think of C/C++ your first thought is move fast and break things? What have they moved fast on and what's breaking for you?
- flohofwoe 5y agoRust is just getting started to see the same problems as C in the 80's (becoming successful enough that multiple competing compiler implementations emerged, which in turn required standardization). I think that the same will happen with Rust (but those can be good things, if it works more like the C committee and less like the C++ committee): first multiple competing implementations (like gccrs) will emerge, and once the situation gets too messy, a proper specification followed by an ISO standard, and a committee to carefully refine and maintain the standard.
- Zababa 5y agoIn the 80's there wasn't internet, which is a huge help to centralize power. For example, look at Python that got popular after internet was a thing: CPython IS Python. People tried alternatives, but popularity brings even more popularity. The same thing happened with Deno recently. Sure, maybe it has a bit of traction, but it's almost nothing compared to Node. It will be the same for Rust and alternative compilers: nobody will use them outside of a few people, that will deal themselves with the consequences.
- zelly 5y agoC++ is pretty much the opposite of moving fast and breaking things. It takes like 10+ years, lots of academic papers and debates, lots of peer review, to get a feature into the ISO standard. The reason it's so bloated is just because of age. Rust is just a single implementation that's CI'ed with nightly releases.