|
> Consequently, faster compile times would not alter my development practices, nor allow me to iterate any faster. I think the web frontend space is a really good case for fast compile times. It's gotten to the point that you can make a change, save a file, the code recompiles and is sent to the browser and hot-reloaded (no page refresh) and your changes just show up. The difference between this experience and my last time working with Ember, where we had long compile times and full page reloads, was incredibly stark. As you mentioned, the hot build with caching definitely does a lot of heavy lifting here, but in some environments, such as a CI server, having minutes long builds can get annoying as well. > Consequently, faster compile times would not alter my development practices, nor allow me to iterate any faster. Maybe, maybe not, but there's no denying that faster feels nicer. |
Given finite developer time, spending it on improved optimization and code generation would have a much larger effect on my development. Even if builds took twice as long.