The transpilation is what everyone publishing Web Apps/pages do these days, it's not needed but most developers don't care, they mostly use whatever bundler default is there.
The **main** lack of ECMAScript feature is a method that is not based on new syntax, doesn't leak arguments, and transform these into an Array. My proposed `slice.apply(index, arguments)` is still not used by transopilers to solve forever in one place the issue so that production code is full of unnecessary boilerplate every single time some dev uses rest parameters for any callback. If there was a method, not based on new syntax, able to be called through `fn.apply(fn, arguments)` so that arguments wouldn't leak, and transpilers can use a single polyfill as entry point to provide that ability, no extra boilerplate would be ever need in production code. I hope what I've said makes sense 👋 On Mon, Jan 14, 2019 at 4:49 PM Boris Zbarsky <[email protected]> wrote: > On 1/14/19 9:47 AM, Andrea Giammarchi wrote: > > rather because of the bloat it produces once transpiled: > > Hold on. > > The transpiling is necessary because of lack of what features in > implementations? > > And what is the set of implementations that will lack those features but > support bindArgs? > > (None of that is an argument against having bindArgs in core per se; I'm > just trying to understand the transpiling issue here.) > > -Boris > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
