3 ms·
Wow, explains a lot. It’s such a shortsighted position for a browser - it’s one of the only platforms that literally can’t have breaking changes, and they want
by nwienert 4y ago
Wow, explains a lot. It’s such a shortsighted position for a browser - it’s one of the only platforms that literally can’t have breaking changes, and they want to bloat it even more?
The entire problem with the web is they keep adding high level half-solutions over and over, many that intersect and almost none that actually solve things at the right abstraction. What we need is lower level primitives and performance. Instead we got Web Components, a disaster, and seemingly a thousand new CSS features (coming only from Chrome) that serve only to further entrench Google.
Simpler and lower level APIs and ruthless work on performance would have given us a far richer platform to target, leading to better interop with cross compiling native tools, better experiences, and less bloat.
Seems like weekly a Google evangelist tweets a gushing, emoji-laden joyous tweet about a new feature they’re shopping tomorrow adding some super arbitrary thing (the latest is some page transition spec which again is such a half-solution). Extend and extinguish!
- aaaaaaaaaaab 4y ago>Seems like weekly a Google evangelist tweets a gushing, emoji-laden joyous tweet about a new feature they’re shopping tomorrow adding some super arbitrary thing (the latest is some page transition spec which again is such a half-solution). Extend and extinguish! They’re going for that juicy promotion, no matter what! The future of the Web be damned…