he/him 
Hot take: JavaScript transpiled features should be as spec compliant as possible, even if it ends up being 10x slower. Ship the slow output to older browsers. Using spec incompliant transforms limits your ability to turn them off safely later.
-
I like this Hot Take, but there's no Standard way to serve up different versions based on UA right now, or to create multiple build targets. If we want people to do it, we have to build the Tools to make it The Default, not the Exception
Two bundles, one for “old” browsers and another for latest browsers is enough. Most people go towards dynamically generating bundles which doesn’t scale. User agent sniffing and explict whitelisting Chrome >VERSION and friends should be enough and should be fairly easy to setup.
-
-
I mean, but even that super simple version needs tooling encouragement or else people won't do it
-
I’m out of touch with how most JS devs are serving static resources.
- 1 more reply
New conversation -
-
-
If you're using browserlist to manage browser versions, there's browserslist-useragent that does that. Single config to rule them all -https://github.com/browserslist/browserslist-useragent …
-
This combined with environments in browserlist can keep the "modern" and "legacy" bundles up to date and maintenance free. So theoretically, JS transplantation, polyfilling, CSS prefixing and serving can occur on dynamic queries like - "last 3 browser versions"
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.