4 ms·

This question may be a bit off topic, so I apologize. I don't work with Rust on anything except homebrew projects, so time is never really of the essence. At wo

This question may be a bit off topic, so I apologize. I don't work with Rust on anything except homebrew projects, so time is never really of the essence. At work, I use scripting languages (Python and Javascript - mostly Python). Is compile time anything except an annoyance, in the real world? Has it really run you up against such close deadlines that an hour of compile time is going to break the company so far as the projects that Rust is being used on? Now, I will fully grant you, I enjoy Rust and like programming in it for fun, but have not kept up on what projects have been made in the wild and professional worlds with it, past Mozilla, TBH. I know a lot of companies are recruiting, but haven't seen much coalesce. Could be my ignorance, though.

assbuttbuttass 5y ago
It's not about missing deadlines, it's about staying focused and not being interrupted while I'm working. At work I use both C++ and go. My experience working on a C++ project is that it takes several minutes just to build, so when I make a change and try to run the unit tests, I find myself wasting a lot of time. I'll often get bored and go on HN for example :) When working on go it's like night and day. Projects mostly compile in less than 30 seconds (unless it has a lot of C++ dependencies). With this pattern I can maintain my focus and continue the modify-build-test loop, I find I end up being a lot more productive.
- anamax 5y ago
  https://xkcd.com/303/ https://xkcd.com/303/
- zozbot234 5y ago
  > when I make a change and try to run the unit tests, I find myself wasting a lot of time You might want to adjust your workflow and make it fit the language better. Avoid relying on unit tests for semantics that can be trivially checked by the type system. Get into the habit of launching builds as part of your work, then check back on the test results after they're done. A build doesn't have to "interrupt" your flow if you plan it correctly.
mamcx 5y ago
I love Rust, but rust being slow annoy me to not end, MUCH more than his complexities. I have worked in Pascal(Delphi), that is a bit more useful in catch issues at comptime. Being able to iterate quickly is also a way to fix errors without loose the train of thought! -- And answering your question: Slow comptimes are directly proportional to burn more energy (no green, cost more). And it impact the cost of that CI pipelines and all that. And yes: I have been hit by slow build times with Rust with serious bugs/problems with customers, unable to move fast enough. One of the worst affect me with a combination of several issues that get slow to note because each one was slow to compile-ship-see effects, enough bad to almost lose a few customers... So, in my mind, the #1 thing I wish Rust has, more than anything, is speed!
Yoric 5y ago
I use Rust a lot, I enjoy it very much, but there are cases in which compile times are real issues, namely in CI. Testing my code means: - downloading a Rust compiler; - downloading/compiling `rustfmt` including dependencies; - downloading/compiling `mx-tester` (the Rust-bassed tool we use for testing) including dependencies; - downloading/compiling the actual project including dependencies. This could be 8-10 minutes wait every time I push code to CI. This also means that debugging CI itself takes days. Admittedly, caching can help a lot. I just haven't configured it yet.

assbuttbuttass 5y ago

It's not about missing deadlines, it's about staying focused and not being interrupted while I'm working. At work I use both C++ and go. My experience working on a C++ project is that it takes several minutes just to build, so when I make a change and try to run the unit tests, I find myself wasting a lot of time. I'll often get bored and go on HN for example :) When working on go it's like night and day. Projects mostly compile in less than 30 seconds (unless it has a lot of C++ dependencies). With this pattern I can maintain my focus and continue the modify-build-test loop, I find I end up being a lot more productive.

anamax 5y ago
https://xkcd.com/303/ https://xkcd.com/303/
zozbot234 5y ago
> when I make a change and try to run the unit tests, I find myself wasting a lot of time You might want to adjust your workflow and make it fit the language better. Avoid relying on unit tests for semantics that can be trivially checked by the type system. Get into the habit of launching builds as part of your work, then check back on the test results after they're done. A build doesn't have to "interrupt" your flow if you plan it correctly.

mamcx 5y ago

I love Rust, but rust being slow annoy me to not end, MUCH more than his complexities. I have worked in Pascal(Delphi), that is a bit more useful in catch issues at comptime. Being able to iterate quickly is also a way to fix errors without loose the train of thought! -- And answering your question: Slow comptimes are directly proportional to burn more energy (no green, cost more). And it impact the cost of that CI pipelines and all that. And yes: I have been hit by slow build times with Rust with serious bugs/problems with customers, unable to move fast enough. One of the worst affect me with a combination of several issues that get slow to note because each one was slow to compile-ship-see effects, enough bad to almost lose a few customers... So, in my mind, the #1 thing I wish Rust has, more than anything, is speed!

Yoric 5y ago

I use Rust a lot, I enjoy it very much, but there are cases in which compile times are real issues, namely in CI. Testing my code means: - downloading a Rust compiler; - downloading/compiling `rustfmt` including dependencies; - downloading/compiling `mx-tester` (the Rust-bassed tool we use for testing) including dependencies; - downloading/compiling the actual project including dependencies. This could be 8-10 minutes wait every time I push code to CI. This also means that debugging CI itself takes days. Admittedly, caching can help a lot. I just haven't configured it yet.