Is there an technical, for web dev noobs explanation written up of what writing single-page / front-end heavy JS gets you?
let's start with: relative to what? native apps or server-side rendered HTML?
-
-
If u read the thread you'll see I specified: web dev à la 2005 when I last did it. Trying to catch up on the field
-
ok cool. the most obvious benefit, then, is the ability to respond to user interaction without a full round-trip 1/
-
if the user has flaky connectivity or lie-fi, this can be significant; lots of apps show diff views of the same data 2/
-
also, allows you to optimistically assume that a change has succeeded (for example chat apps) and deal with failure only then 3/3
-
That helps. I get why AJAX is useful. I don't get why youd want to render all HTML in JavaScript as opposed to just the dynamic bits
-
quite often they are deeply intertwined and rendering via templates is the best way to be sure you can do the dynamic parts.
-
Glimmer (one of those newfangled JS thingies) takes tons of advantage of the static parts, but not having to divide the code 1/
-
architecturally between static and dynamic is a net reduction in mental overhead and complexity in my opinion 2/2
- 1 more reply
New conversation -
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.