This was last year. "Guys, guys, we need to convert everything to ES6." Our mainly users were elderly people with old devices. So we did. Many resigned shortly.

The users really shouldn not see any difference between using ES5 or ES6, the benefit (or disadvantage) of using ES6 is really only for the developers, but if an app or web site is already built on a stack, redoing it just because there is this shiny new toy out is ridiculous.

@RinseRepeat most devices hate the "arror function" and more. what I remembered was we never liked working there anyways. when new toys comes out, we must use it. if we can avoid bugs, we will.

@sylar yes, ES6 is still not that widely supported, but you can always transpile it to ES5 with Babel to get that support.now you might ask, why code in ES6 if the code is going to be converted into ES5? Again, it's all for the advantage of the dev, as ES6 offers a lot of syntatic sugar.

well, refactoring code can be good as you clean it up, especially if you redo it for es6 and transpire down to es5 as long as es6 is still widely unsupported.

I don't really see the issue with this

@doskallemaskin ES6 for the sake of it can be dangerous. I'm still trying to fix the mess of one developer (who was already fired). When he learned about ES6 he decided we needed to turn everything into ES6. He never learned it enough, now we have a bunch of broken code with lots of bad practices, and the code worked just fine before.
If it isn't broken, don't fix it.

@RinseRepeat yeah pfc it should be fixed in a dev branch or something and never left undone. it's half-true to never fix unbroken stuff tho imo.

The issue seems more to be lack of a proper TA and planning on convention and what es6 is etc.