Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ECMAScript 2015 Approved

ecma-international.org

Post reply on HN
Print view View original

31–40 of 108 posts

Re: ECMAScript 2015 Approved

#31

Post by aaron-lebo »

casus wrote: post #29
fintler wrote: 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.

> "a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc" Part of the problem with the Javascript ecosystem is that you have to use so many different tools/libraries to create a "simple" app.

That's true to an extent, but gulp/babel are something you setup once and forget. npm is a package manager, the others are libraries. It's no different than saying that someone used pip, Flask, Requests, and xlrd for a Python project. They're just libraries.

Re: ECMAScript 2015 Approved

#32

Post by [deleted] »

peter_l_downs wrote: post #26
fintler wrote: 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.

I've been away from JS for about 10 months and... cool, but, fuck, that changed quickly. Time to get caught back up to speed. Is ES6 now actually viable, in that it's supported by most users' browsers? If not, are there popular compilers for ES5?

[deleted]

Re: ECMAScript 2015 Approved

#33

Post by serve_yay »

peter_l_downs wrote: post #26
fintler wrote: 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.

I've been away from JS for about 10 months and... cool, but, fuck, that changed quickly. Time to get caught back up to speed. Is ES6 now actually viable, in that it's supported by most users' browsers? If not, are there popular compilers for ES5?

"Everyone" is using Babel now. A lot of ES6 features are making their way into browsers and node, but there's so much variation that a transpile step is needed. Babel is nice but currently quite slow. Babel has a REPL you can play with here: http://babeljs.io/repl/#?experimental=true&evaluate=true&loo...

Re: ECMAScript 2015 Approved

#34

Post by trose »

killface wrote: post #20
sirsuki wrote: 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.

That changes a lot if your target market is big enterprise customers. Oh you don't support IE9? Well say goodbye to that market share.

Re: ECMAScript 2015 Approved

#35

Post by rattray »

fintler wrote: 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.

It's even better if you use `yield` or `async/await`:

    activate(params) {
      let fabric_response = yield this.http.get(`${ this.url_base }/fabrics`)
      return fabric_response.content.map( fabric => {
          let cluster_response = yield this.http.get(`${ this.url_base }/fabrics/${ fabric.name }/clusters`)
          if(fabric.clusters_exist) {
              this.fabrics.push({"name": fabric.name, "clusters": cluster_response.content});
          }
      });
    }
EDIT: note that I am very sleepy and probably did a poor job of this =)

Re: ECMAScript 2015 Approved

#36

Post by bryanlarsen »

killface wrote: post #20
sirsuki wrote: 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.

You just need to find a tent-pole feature and a reason to use it.

For example: "This browser requires WebGL" -> IE11 and up.

Re: ECMAScript 2015 Approved

#38

Post by cnp »

casus wrote: post #29
fintler wrote: 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.

> "a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc" Part of the problem with the Javascript ecosystem is that you have to use so many different tools/libraries to create a "simple" app.

Once you do it once, its done. Also, tons of scaffolds out there to choose from / tweak. This sort of flexibility is a good thing.

Re: ECMAScript 2015 Approved

#39

Post by cnp »

gravity13 wrote: post #24
Strilanc wrote: post #18

Earlier quoted context omitted.

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

After working with es6 for a bit (with babel), I still think I prefer CoffeeScript mostly because it's annoying to ensure brackets/parenthesis are closed properly.

Its funny, I used to really enjoy CoffeeScript but since Babel / ES6 has come out I can't stand it anymore! ES6 has just the right amount of syntax, with lots of optionals too (semicolons, no brackets when writing function expressions, etc).

Re: ECMAScript 2015 Approved

#40

Post by nobleach »

casus wrote: post #29
fintler wrote: 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.

> "a small app built on ec6/7 babel, npm, jspm, system.js, aurelia, gulp, etc" Part of the problem with the Javascript ecosystem is that you have to use so many different tools/libraries to create a "simple" app.

Every language these days has its "stack" for development. Sure you could sit down with vim and javac and write a "simple app". But once you use Gradle/Maven to handle dependencies and build process. Once you use a nice unit testing framework... Why on earth would you not just fire it up and tune it for every project? Ruby, C# and every other language I've used has this "development stack" mentality, and now when I try out new languages, I research setting up the stack first!
Post reply on HN