Another way to think about the PIG & reach/richness frontier and how "modern" JS pulls you away from it: How many bounced Android users is IE11 support worth?https://twitter.com/slightlylate/status/1233204165809061889 …
-
-
Replying to @slightlylate
Hmm, it isn't a technical necessity to choose between IE11 and Android, is it? I thought nomodule was the way forward there
2 replies 0 retweets 1 like -
Replying to @zachleat
That assumes that ~all the bloat is down to transpiler/polyfill overhead, which at least in the case of something architected for the Old World (e.g. React) isn't the case. Module-baesd-and-lightly-transformed React is still a huge multiple of Preact in size, e.g.
2 replies 0 retweets 2 likes
At the frontier, choices are tradeoffs. You can tell you aren't anywhere near the frontier when you can swap in an alternative that's 10x smaller and lose almost no practical compat:https://preactjs.com/about/browser-support/ …
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.