4 ms·
What does fast "natural implementations" mean? Runtime? Compile-time? Because if one sacrifices the latter for the former, I think that skirts over the main ben
by yowlingcat 4y ago
What does fast "natural implementations" mean? Runtime? Compile-time? Because if one sacrifices the latter for the former, I think that skirts over the main benefit.
With dynamic, interpreted languages that have effectively zero compile-time, one can achieve significantly tighter iteration cycles across a team, ending up limited more by test suite runtime than by slow edit/recompile cycles. This leads to higher productivity across an engineering organization with a quickly evolving codebase. Not important for all use cases, but pretty critical for many.
- kaba0 4y ago> effectively zero compile-time, one can achieve significantly tighter iteration cycles across a team I don’t know what machines do people develop on, but on a fairly old laptop I get practically instantaneous iteration with incremental compiles with Rust, which is one of the slowest compiling languages. I honestly can’t imagine where is this supposed slow compiles in case of something like Java - like sure one can create some monstrosity of a build definition, but if some competent person wrote it it is just as fast as an interpreted language. Hell, it can do hot swapping just fine.