4 ms·

Interesting question, what about it? Would the incremental cost of more people learning the language mean that there'd be less output in the short term, thus of

Interesting question, what about it? Would the incremental cost of more people learning the language mean that there'd be less output in the short term, thus offsetting the benefit of "RIIR"? Rust can be a difficult language, but I think that for most common usecases (web), we could reach reasonable proficiency in a few months/years. There's also other interesting aspects like more tooling written in Rust, benefiting some of the existing languages, with a positive benefit to development time. If there are say 1'000'000 CI JS CI jobs running at any time, and compile/transpile times are reduced from say 3 minutes to 30 seconds, would developers be more productive and thus produce more (higher energy) or complete work quicker (less energy)?

isomel 5y ago
There is also the compilation time. So it depends if the program is meant to be run about as many time as being compiled (during development) Or if the program is compiled once, and run millions of times
- allisdust 5y ago
  Are there any use cases where its beneficial to compile frequently?
  - lostdog 5y ago
    > Are there any use cases where its beneficial to compile frequently? Writing software? It's very useful to check your work. If can only verify your work slowly, then you will verify less frequently. This means you will work on a large feature but only check at the very end. This can be very inefficient, and checking for mistakes as you write code is much more efficient.
collegeburner 5y ago
> we could reach reasonable proficiency in a few months/years. This is silly, I hear rust called hard to learn but I picked it up in about 2 weeks of hacking around a bit with a side project and was quite proficient with working in web. By 1 month or so, maybe 1.5k loc, I was good with it. Only thing is there are still sometimes interesting features or better ways to do things that I find.

isomel 5y ago

There is also the compilation time. So it depends if the program is meant to be run about as many time as being compiled (during development) Or if the program is compiled once, and run millions of times

allisdust 5y ago
Are there any use cases where its beneficial to compile frequently?
- lostdog 5y ago
  > Are there any use cases where its beneficial to compile frequently? Writing software? It's very useful to check your work. If can only verify your work slowly, then you will verify less frequently. This means you will work on a large feature but only check at the very end. This can be very inefficient, and checking for mistakes as you write code is much more efficient.

collegeburner 5y ago

> we could reach reasonable proficiency in a few months/years. This is silly, I hear rust called hard to learn but I picked it up in about 2 weeks of hacking around a bit with a side project and was quite proficient with working in web. By 1 month or so, maybe 1.5k loc, I was good with it. Only thing is there are still sometimes interesting features or better ways to do things that I find.