JSC loves ES6

#1

Post by pizlonator » Mon, Jun 05, 2017, 5:45 PM UTC

Re: JSC loves ES6

#2

Post by jacobolus » Mon, Jun 05, 2017, 10:13 PM UTC

I’ve been staying away from most new ES6 features because when I tested them a year ago (either transpiled or with native support) they were slow as molasses in every browser I tried. Hopefully having some better benchmarks gets Firefox and Chrome developers to also get to work on this.

Re: JSC loves ES6

#3

Post by hzoo » Mon, Jun 05, 2017, 10:14 PM UTC

jacobolus wrote: post #2

I’ve been staying away from most new ES6 features because when I tested them a year ago (either transpiled or with native support) they were slow as molasses in every browser I tried. Hopefully having some better benchmarks gets Firefox and Chrome developers to also get to work on this.

Yeah a good idea. I was thinking we could make a similar table to compat-table (maybe using six-speed or this) that we could use as data to https://github.com/babel/babel-preset-env so that Babel could compile based on the compiled speed relative to native support. Haven't really looked into in much yet (if anyone is interested, let me know)

Basically, if there is native support but it's not as fast as compiled/polyfilled we could continue to compile.

Re: JSC loves ES6

#4

Post by hoodoof » Mon, Jun 05, 2017, 10:21 PM UTC

A bit odd that they don't call it ES2015.

Re: JSC loves ES6

#5

Post by caiob » Mon, Jun 05, 2017, 10:25 PM UTC

Worth noting that Safari Technology Preview was the first browser to support all of ECMAScript 2016+ features.

* http://kangax.github.io/compat-table/es2016plus/

Re: JSC loves ES6

#6

Post by iddan » Mon, Jun 05, 2017, 10:27 PM UTC

Another great reason to migrate Electron to WebKit. With WebKit and JSC Electron will be faster and will use a zero amount of RAM and battery!

Re: JSC loves ES6

#7

Post by iddan » Mon, Jun 05, 2017, 10:28 PM UTC

hoodoof wrote: post #4

A bit odd that they don't call it ES2015.

It will look bad they are two years behind.

Re: JSC loves ES6

#8

Post by smitherfield » Mon, Jun 05, 2017, 10:28 PM UTC

caiob wrote: post #5

Worth noting that Safari Technology Preview was the first browser to support all of ECMAScript 2016+ features. * http://kangax.github.io/compat-table/es2016plus/

Although IIRC Chrome and/or Firefox had all but guaranteed tail-call optimization (not a source code-level feature, obviously) first.

Re: JSC loves ES6

#9

Post by k__ » Mon, Jun 05, 2017, 10:31 PM UTC

iddan wrote: post #6

Another great reason to migrate Electron to WebKit. With WebKit and JSC Electron will be faster and will use a zero amount of RAM and battery!

Doesn't Electrino basically try this?

Re: JSC loves ES6

#10

Post by Androider » Mon, Jun 05, 2017, 10:37 PM UTC

The benchmark at the bottom showing how far behind Firefox has fallen on JS performance is pretty telling. It confirms my own recent observation that Firefox is at least 3-6 times slower in practice for the particular app I'm working on.