It's true; I'm also seeing SO MUCH transpiler bloat....they're like zombie polyfills. Not even polyfill.io can kill them!
-
-
Replying to @slightlylate @robwormald and
What could polyfill.io do to help even more?
2 replies 0 retweets 0 likes -
Replying to @JakeDChampion @robwormald and
Not much, I fear. The Transpiler overhead ends up in the first-party binary = (
2 replies 0 retweets 0 likes -
Replying to @slightlylate @JakeDChampion and
*Such* a pain doing targeted transpilation. By default webpack still shipping old non-es6 compat uglify (will blow up if you turn off Babel)
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @slightlylate and
I guess my main point is, by some sick twist of fate, we professionals are depending on stuff maintained by volunteers, and doing our best.
1 reply 0 retweets 1 like -
Replying to @AdamRackis @slightlylate and
Part of my working job is maintain polyfill.io :-)
1 reply 0 retweets 3 likes -
Replying to @JakeDChampion @slightlylate and
What's polyfill.io use case? At this point isn't it usually all or nothing? IoW IE, which needs everything, or Chrome which needs nothing?
3 replies 0 retweets 0 likes -
Replying to @AdamRackis @JakeDChampion and
Like, are there browsers today that need Promise, Symbol and Set, but already have Map and Array.from ?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @JakeDChampion and
Chrome 41 as Googlebot befuddles expectations.
2 replies 1 retweet 2 likes -
Replying to @wycats @AdamRackis and
at least you know its Chrome 41 now ¯\_(ツ)_/¯
1 reply 0 retweets 2 likes
Which do you prefer, dying slowly of poison or being shot in the head?
-
-
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.