3 ms·

wait a second, the improvement is 30 seconds to 10-15? how is that workable? that would drive me insane maybe i'm spoilt, but modern frontend with hot reloadin

wait a second, the improvement is 30 seconds to 10-15? how is that workable? that would drive me insane maybe i'm spoilt, but modern frontend with hot reloading on save is just about instant. even when i used kotlin (spring boot ~2.3), re-running a test with the intellij compiler took around 1 second. is kotlin-js really usable with that performance?

__s 2y ago
this may be the effect of what people are used to. Going from 30 to 15 is huge, even if it's awful compared to a couple seconds / hot reloading. I've worked on projects where the development loop required deploying to a test environment. You get used to programming without the feedback loop (not to say that this feedback loop shouldn't be sought after, only that one adapts to their circumstances)
- mdaniel 2y ago
  I also hypothesized that working in an actual statically and strongly typed language leads to less "save, reload, pray" loops than a typical front-end developer may have gotten used to
jillesvangurp 2y ago
It's very usable. What you loose in performance, you gain in confidence provided by a statically compiled language. So, you can simply go longer in between reloads without risking too much fall out. If it compiles, it will probably run without a lot of weirdness. So there's less need to feel insecure whether things will still run. Also, I should point out that this is on a largish three year old code base. Re-running tests without recompiling is similarly fast with kotlin-js. A Spring integration test with some code in main and test needing recompilation and the Spring Boot start up time will also set you back 15-20 seconds or so. And as I pointed out webpack is at least half of the time you are waiting these days. IMHO, getting rid of that and replacing it with something faster could be worthwhile.

3 ms·

wait a second, the improvement is 30 seconds to 10-15? how is that workable? that would drive me insane maybe i'm spoilt, but modern frontend with hot reloadin

by willsmith72 2y ago

__s 2y ago
this may be the effect of what people are used to. Going from 30 to 15 is huge, even if it's awful compared to a couple seconds / hot reloading. I've worked on projects where the development loop required deploying to a test environment. You get used to programming without the feedback loop (not to say that this feedback loop shouldn't be sought after, only that one adapts to their circumstances)
- mdaniel 2y ago
  I also hypothesized that working in an actual statically and strongly typed language leads to less "save, reload, pray" loops than a typical front-end developer may have gotten used to
jillesvangurp 2y ago
It's very usable. What you loose in performance, you gain in confidence provided by a statically compiled language. So, you can simply go longer in between reloads without risking too much fall out. If it compiles, it will probably run without a lot of weirdness. So there's less need to feel insecure whether things will still run. Also, I should point out that this is on a largish three year old code base. Re-running tests without recompiling is similarly fast with kotlin-js. A Spring integration test with some code in main and test needing recompilation and the Spring Boot start up time will also set you back 15-20 seconds or so. And as I pointed out webpack is at least half of the time you are waiting these days. IMHO, getting rid of that and replacing it with something faster could be worthwhile.