3 ms·
Even if generation functions are not supported - its a tradeoff that is worth making since very few of our users use IE11. That is not my main concern. Babel c
by wrong_variable 10y ago
Even if generation functions are not supported - its a tradeoff that is worth making since very few of our users use IE11.
That is not my main concern. Babel can wrap the code in 10 functions for all I care ( performance is also not a concern since we are not sending rockets to mars - just another technology sweatshops trying to sell viagra )
The wrapped function throws errors - since apparently you need to download some babel plugins for it to work. (ノಠ益ಠ)ノ彡
- Klathmon 10y agoIt's not just IE11, it's Safari 9 and older, iOS 9 and older, and Android 5.0 and older. Generators are unsupported on all of them.
- tracker1 10y agoAnd if you're public facing, IE9-11 may be too big combined to not support.
- coldtea 10y ago>That is not my main concern. Babel can wrap the code in 10 functions for all I care ( performance is also not a concern Babel code is actually faster than the native implementation of most of the ES2015/6 features atm. >The wrapped function throws errors - since apparently you need to download some babel plugins for it to work. (ノಠ益ಠ)ノ彡 So you forgot to download some plugins and it's Babel's fault? And, sorry, where does the entitlement come from? It's you who needs and uses Babel, even imperfect and buggy as it is, to get the job done, not the inverse.
- wrong_variable 10y agoAs I have mentioned above, I do not write ES6/ES2015/ES2016... Its the entire web community writing code in a barely function compiler.
- coldtea 10y ago>I do not write ES6/ES2015/ES2016... So maybe not the best person to comment on the state of its tools? >Its the entire web community writing code in a barely function compiler. "I didn't include some plugins so the compiler couldn't work" != "barely functioning compiler".