4 ms·

Seems to be like another thing that will end up in my code reviews of esoteric wind-bags.

• erikpukinskis 11y ago
  Is it just me or is ES6 kind of ruining Javascript by adding dozens of ways of solving problems that plain JS is perfectly capable of solving if you know how to use it? Should I try harder to see the usefulness of it? Right now all it seems to have done for me is make it impossible to use NPM modules because everything is targeting a different runtime and stuff that expects JavaScript breaks other libraries that expect ES6 and vice versa. I'm forced now to use what feels like a beta language in production because a handful of key libraries now require ES6. I am seriously considering just forking every library that ports to ES6, which is preposterous, but I don't know what else to do. The whole point of JavaScript in my mind was that it runs everywhere, on every obscure browser and any machine with a node executable. ES6 has ruined what was Javascript's most unique and most powerful feature.
  • iamleppert 11y ago
    I couldn't agree more with you. What ever happened to keeping the language small, and allowing the community to provide for useful abstractions on top of it? Now we have a bloated spec. Seriously. Fat arrow syntax with explicit scope? Bind() works just fine, thank you. And this isn't about fear of change. Change should only be for legitimate purpose. When I detect any trace of change for stylistic issue, I snear.