[Xevi]

I even have the browser and code on the monitor at the same time. And with pretty much all modern web frameworks you have a dev server that automatically does hot module replacement, so you instantly see your changes without reloading anything yourself.

[nkozyra]

I've never seen a hot reload that worked fast enough to not be annoying.

React does it all quickly when all it's re processing is css but anything js related and it seems not to be able to treeshake down to bare minimum updates.

We're talking 750ms to 1.5s, and I admit it's still a marvel compared to things I used to have to deal with, but it's still enough to feel cludgy.

Flutter is another example of this. It's not _slow_ but if I'm sitting there waiting for even a bit I'm less likely to use the feature as an incremental tool rather than batch a bunch of things before looking or tabbing over.

[dmix]

I use a vue dev server daily (both with webpack previously and now with the way faster vite) and it's pretty much instant.

These projects only recompile the code that changes, then via chunking the browser only reloads a tiny specific .js file that contained that one component matching the vue-route, so usually 10-30kb refresh (and it loads about ~10x small .js files per page), which happens before I can tab back or notice when widescreened.

Previously when I used the slower Webpack without chunking it started to take time when the project grew large. But that was long ago (3 years ago?).

[randomsearch]

> I've never seen a hot reload that worked fast enough to not be annoying.

Then you, my friend, have never used Vite.

[FractalHQ]

As a Svelte developer, I can’t remember the last time I had to work _without_ an instant HMR with optical state preservation. That sounds like a nightmare and a huge productivity killer.