Kinda sad seeing people get excited over flatMap or trim functions... Looks like JS will slowly get a standard library over the coming years... And you need a JS to JS compiler to deploy this......
Kinda sad seeing people get excited over flatMap or trim functions... Looks like JS will slowly get a standard library over the coming years... And you need a JS to JS compiler to deploy this... If I'm already adding an extra step if compilation, why wouldn't I go with something like Typescript or similar instead? As stuff becomes standard more and more will be added, so you can't get off Babel unless you're using ES5 directly.
Maybe in the immediate future, but it doesn't take long these days to get new features. Evergreen browsers have finally reached the majority and that means that features can go from 0% support to...
And you need a JS to JS compiler to deploy this...
Maybe in the immediate future, but it doesn't take long these days to get new features. Evergreen browsers have finally reached the majority and that means that features can go from 0% support to >95% within a month.
Kinda sad seeing people get excited over flatMap or trim functions... Looks like JS will slowly get a standard library over the coming years... And you need a JS to JS compiler to deploy this... If I'm already adding an extra step if compilation, why wouldn't I go with something like Typescript or similar instead? As stuff becomes standard more and more will be added, so you can't get off Babel unless you're using ES5 directly.
Maybe in the immediate future, but it doesn't take long these days to get new features. Evergreen browsers have finally reached the majority and that means that features can go from 0% support to >95% within a month.
Shouldn’t you at least be able to use ES6? After four years, it should be well supported enough.
I was hoping the pipeline operator would make it into this year's specification when I first heard about it.
Reposting because I got the title wrong originally.