26 ms·
> Anyway I stopped the project when Rust released their first version without garbage collection. It seems to me they solved all my concerns and they didn't eve
by lelanthran 5y ago
> Anyway I stopped the project when Rust released their first version without garbage collection. It seems to me they solved all my concerns and they didn't even need to integrate C itself.
Illustrates why projects don't do this:
> If you're breaking backwards compatibility anyway, why not go all the way?
Rust usage, even with millions of dollars of marketing and eleven years of hype, is still almost a rounding error in terms of usage.
- tinco 5y agoMillions of dollars in marketing? 1.0 was released in 2015. Yeah, it will take a couple years more before a 6 year old language will replace a 40 year old language, but we'll get there no doubt. But that's not the right comparison. The use of the C language itself is a rounding error compared to all the languages that replaced it. Java, C#, C++, Python, Javascript, Go, they all replaced most use cases of C in modern programming. Rust is just attacking the last vestiges of C's usefulness.
- yobbo 5y ago> is still almost a rounding error in terms of usage Within the tiny set of scenarios where Rust is applicable as of now, isn't it completely dominating? It's dominating in hype and excitement for toy and pet projects. This is just the first few steps. Too few people have dabbled enough yet. The next step is enough stability/maturity that more open source and maybe fang infrastructure can use it. And when the reasoning behind this becomes widely digested, most "green field" projects will choose Rust. But that may be ten years away?
- carols10cents 5y agoFAANG are already using Rust today.