Haha, yeah but if you preserve state and touch the schema in any way it'll break on reload. Unless you code in migrations just for dev :/
Here's my take on live reloading JS during development (and why I tend to stick to lo-tech solutions)pic.twitter.com/D0xVL8XkQV
-
-
-
I tried the "app is just a module" approach in the past, but found that bc it needs to operate on history and routing it's best to framework
- 1 more reply
New conversation -
-
-
I’m biased but I enjoy the budo way. Inject CSS, hard reload everything else. Especially b/c I work with stateful webgl/canvas APIs mostly
-
Yeah, this is what we're gonna be doing with Bankai too I think. Gonna use the CSS reload module you linked a while back :D
End of conversation
New conversation -
-
-
and then you're more likely to embed navigation states in the url or indexedDB instead of non-persistent state vars
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks! Finally someone says it. Thought I was alone on the lo-tech lane :/
-
Nope. I also do not use HMR for JS. But for CSS it's nice, because it preserves DOM state :)
End of conversation
New conversation -
-
-
I'm with you on this, exactly how I do things
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I've been thinking that we don't take advantage of history state/query params more often for app state. Really makes live-reload easy.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.