3 ms·

I don't think using a vscode plugin as an example of Rust not being ready is very fair. You could always fix the issue yourself, it is open source you know. My

I don't think using a vscode plugin as an example of Rust not being ready is very fair. You could always fix the issue yourself, it is open source you know. My original point was that we shouldn't be building monolithic projects in a single language, but if there is an absolute requirement for it, Rust compile times aren't that bad. C++ also has very long compile times, it just comes with the territory. The reason Go can compile in under a second is because they purposefully keep the language specification simplistically small. I'm not recommending Rust nonchalantly. I write rust every day professionally, and I basis my opinions on the experiences I've had with it in that environment.

banachtarski 8y ago
It is fair because there are very few options for authoring Rust code. Regardless of who is responsible, a robust and working toolchain is sort of the minimum bar for a language, and yes it's open source, and yes I've looked at the code, but no it's not worth the time right now because better options exist. I'm super familiar with C++ compile times but again, there exist a lot of infrastructure to at least help with that or eliminate it completely (with some tricks). I'm not saying Rust will never get there, but for me, too soon too early.