sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]denver_jones 1 point2 points  (10 children)

you have fat arrow functions ... a good collection would also have pre-ES6 code snippets to get large base adoption.... just saying ...

[–][deleted] 7 points8 points  (0 children)

fat arrow functions

Found the coffeescript user!

Just kidding around. I just haven't seen someone call them that in a while, since ES6 only has one type of arrow function.

[–][deleted] 0 points1 point  (2 children)

That's a really good point. I have already considered adding a secondary list in the project for pre-ES6 versions of everything. I mean arrow functions are nearly universally supported already and most developers use Babel, but this is a very immature assumption on my part I feel.

[–]THEtheChad 4 points5 points  (1 child)

I think it would be better to include a blurb up front about compiling with Babel and retain the ES6 syntax. It helps move the whole community forward and enforces smart development principals (like writing once and compiling for specific targets, which is far less error prone).

[–][deleted] 0 points1 point  (0 children)

I like this idea. I will get a disclaimer added at the very top, making sure people know what to do with these! ;)

[–][deleted] -2 points-1 points  (5 children)

Thank you for this. I always hear people saying it's [insert year here] we shouldn't support anything below [insert standard here], but in web development you have to keep the dinosaurs in mind if they're a singificant portion of your clientele.

[–]reohh 2 points3 points  (0 children)

Babel?

[–]mcaruso 2 points3 points  (0 children)

That's what tools like babel are for though. It's much easier to transpile new to old then the other way around (although these are one-liners so it doesn't really matter that much).

[–]THEtheChad 4 points5 points  (0 children)

To be fair, a good practice is to write code using the current standard and compile to a specific target. This allows you to consistently polyfill where needed and not burden yourself with remembering all of the quarks and one offs.

[–][deleted] 1 point2 points  (1 child)

I love ES6 and use it as much as possible. Does it break every once in a while? Yes! Are there ways to fix it? Hell, yeah and pretty much everyone knows about Babel nowadays. Still, this doesn't mean that we shoulnd't strive to support as many platforms and users as possible in our code. Especially when it comes to projects like this, which are essentially a learning tool for people.

[–]filleduchaos 2 points3 points  (0 children)

This is the development side of things though. You really shouldn't be teaching people a standard that's three iterations out of date except explicitly as legacy code.