The distinction here is important. I keep coming back to package management in Go. It’s not that Google engineers don’t acknowledge its a problem, it’s that they just *don’t have that problem themselves* and that shapes how they approach resolving it.
-
-
(which is not to take anything away from the value of standards, but choices about compiled-down interfaces w/ one impl aren't standards)
-
I'd love it if this pathway also had a factor for user benefit weighting...some sort of peer review to do more than tribally self-congratulate.
- 7 more replies
New conversation -
-
-
This is evidenced by all the "how we switched from X to Y" at literally every conference.
-
We also had this whole cycle in the Rails with server side rendering being the solution to performance, then the browser added some features and perf improvements and we cycled out. Literally the exact same thing is happening with SSR now in React.
End of conversation
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.