Live data from Hacker News

ECMAScript 2015 Approved

ecma-international.org

11–20 of 108 posts

Re: ECMAScript 2015 Approved

#11
It's about fricken time! Talk about procrastination!

Now I have to wait for browsers to get off their little snowflake asses and update. Oh wait then there is all those paranoids who use WinXP with IE8. Damn it, I'll be dead by the time this stuff is available universally.

Re: ECMAScript 2015 Approved

#12

FYI, ECMAScript 2015 is also known as ES6.

Because of their switch to use a year instead of a version number, do they plan on doing these ES enhancements more often?

I think that's the plan. Whatever the committee can agree on and ratify by December 2016 will be dubbed "ES 2016" and so on.

Re: ECMAScript 2015 Approved

#14
post #11

It's about fricken time! Talk about procrastination! Now I have to wait for browsers to get off their little snowflake asses and update. Oh wait then there is all those paranoids who use WinXP with IE8. Damn it, I'll be dead by the time this stuff is available universally.

One of the reasons why I'll go with Dart or TypeScript or whatever anyway. ;)

Re: ECMAScript 2015 Approved

#16
If you've been focusing on another language for a few years, you might not recognize JavaScript anymore. It's pretty awesome now.

Here's an example of what it looks like: http://pastebin.com/raw.php?i=yEB4mrty

As someone who usually works with C, Scala, and Java -- I'm currently working on a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc. It's been a great experience so far.

Re: ECMAScript 2015 Approved

#17
post #16

If you've been focusing on another language for a few years, you might not recognize JavaScript anymore. It's pretty awesome now. Here's an example of what it looks like: http://pastebin.com/raw.php?i=yEB4mrty As someone who usually works with C, Scala, and Java -- I'm currently working on a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc. It's been a great experience so far.

Yikes! Don't blame ES6 for this mess :P

Re: ECMAScript 2015 Approved

#18
post #16

If you've been focusing on another language for a few years, you might not recognize JavaScript anymore. It's pretty awesome now. Here's an example of what it looks like: http://pastebin.com/raw.php?i=yEB4mrty As someone who usually works with C, Scala, and Java -- I'm currently working on a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc. It's been a great experience so far.

Nit: single line lambdas can be written like `a => a + 1` instead of `a => { return a + 1 }`. Cuts the amount of bracket nesting.

Re: ECMAScript 2015 Approved

#19
post #16

If you've been focusing on another language for a few years, you might not recognize JavaScript anymore. It's pretty awesome now. Here's an example of what it looks like: http://pastebin.com/raw.php?i=yEB4mrty As someone who usually works with C, Scala, and Java -- I'm currently working on a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc. It's been a great experience so far.

Is "@inject(HttpClient)" ES6 too? I don't recognize it but I haven't memorized all the new capabilities yet.

Re: ECMAScript 2015 Approved

#20
post #11

It's about fricken time! Talk about procrastination! Now I have to wait for browsers to get off their little snowflake asses and update. Oh wait then there is all those paranoids who use WinXP with IE8. Damn it, I'll be dead by the time this stuff is available universally.

At some point, you just need to stop caring about those people. I know some of you can't professionally, but personally, there's no need to even pretend to support IE <= 11. If they want to run an old os and old browser, they don't get to use my service. No sweat off my balls.
Post reply on HN