I'm increasingly convinced that only browsers can change web developer behaviour -- the current situation is untenable: either we fix this, or the idea of "having a job making websites" will become an anachronism.https://twitter.com/slightlylate/status/996195317493129216 …
-
-
I'd be curious for some analysis on what bits are growing, if you understand what I'm asking. Like, as in, what is it that is trying to be done that we could avoid here with better features and still meet expectations
-
The community is largely rejecting non-user-space answers. Many causes, but all lead to bad client-side experiences.
- 9 more replies
New conversation -
-
-
All because of low bar of development and everyone truing to lower it, making damn easy tools to jump in without thinking, and those tools often have a very big cost. I don't know why people do it. They say to have more devs, but more devs isn't more quality for the web.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is it really the root cause or a symptom though? Platforms such as RN have an easier happy path to perf (far from perfect, but still), yet it's running JSCore in interpreter mode.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Webpack… it you’re not careful, it will pack the universe.
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.