3 ms·

Not OP but i keep trying and the tools still have a long way to go and compile times are abysmal (even relative to C++). For example, https://github.com/rust-la

Not OP but i keep trying and the tools still have a long way to go and compile times are abysmal (even relative to C++). For example, https://github.com/rust-lang/rls-vscode/issues/237 https://github.com/rust-lang/rls-vscode/issues/237 this issue that has persisted for over a year with no signs of being fixed. With C++, in spite of its warts, I can still be productive just because of the ecosystem around it. Rust was something I was gung-ho about, but after repeated attempts to create a medium/large project, I am still in a wait and see mode. Moreover, it's just not powerful enough. Many features are coming in, but they break the compiler and you end up needing to work off nightly regardless. I think it's a good effort, but people just recommending the Rust train nonchalantly really need to step back and check their biases.

ilovecaching 8y ago
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.

ilovecaching 8y ago

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.