"Shifting the conversation away from actual user experiences to team-level advantages enables a culture in which the folks who receive focus and attention are developers, rather than end-users or the business." Brilliant spot on piece by @slightlylate.
https://infrequently.org/2018/09/the-developer-experience-bait-and-switch/ …
-
-
That's where I see a many fail when using SSR; eg rendering large view state in the init resp and yet still needing that JS to make it work. Devs perceive this will result in gains (common trope, SSR = faster) when that's just not the case.

-
hmmm...is there a performant way to do both? I want to provide quickly rendered content with routing and animated transitions and all the other bells and whistles while also making my app the smallest it could possibly be...I think this is the area I just don't understand

- 1 more reply
New conversation -
-
-
hmmmmm...so sending enough JS for your app, in the appropriate PRPL doses, is chill, just leave the framework at home, so as not to push another mini OS on top of the browser, on top of the OS.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.