JSC loves ES6 • Hacker News Board

Re: JSC loves ES6

#11

Post by pizlonator » Mon, Jun 05, 2017, 10:39 PM UTC

smitherfield wrote: post #8

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.

I don’t think that’s right. Source?

Re: JSC loves ES6

#12

Post by pizlonator » Mon, Jun 05, 2017, 10:40 PM UTC

hoodoof wrote: post #4

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

We were calling it ES6 since before it was called ES2015.

Re: JSC loves ES6

#13

Post by pizlonator » Mon, Jun 05, 2017, 10:43 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!

Dunno about zero. Sounds hard.

Re: JSC loves ES6

#14

Post by emsal » Mon, Jun 05, 2017, 10:46 PM UTC

k__ wrote: post #9

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?

Currently it looks like Electrino only supports macOS. Doesn't it sort of defeat one of the purposes of using a web-based framework for desktop apps if it's not even cross-platform?

Re: JSC loves ES6

#15

Post by vmasto » Mon, Jun 05, 2017, 10:47 PM UTC

I really wish we would stop calling it ES6. Browser vendors should be especially careful to call ES2015 by its correct name and help stop perpetuating the confusion (ES6, ES7, ES2016, ES2017, you can see how this quickly gets confusing).

Re: JSC loves ES6

#16

Post by ergothus » Mon, Jun 05, 2017, 10:50 PM UTC

vmasto wrote: post #15

I really wish we would stop calling it ES6. Browser vendors should be especially careful to call ES2015 by its correct name and help stop perpetuating the confusion (ES6, ES7, ES2016, ES2017, you can see how this quickly gets confusing).

ES6 is 3 syllables. ES2015 is 6 or 7 (depending if you say "twenty fifteen" or "two thousand fifteen").

I'm a dev. I'm lazy. I have no particular objection to the idea of moving away from ES6 as a name, but if the new name isn't more useful, it's not going to gain any ground.

Re: JSC loves ES6

#17

Post by franciscop » Mon, Jun 05, 2017, 10:51 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.

Do you mean that you saw actual differences when using Javascript in a normal website? Or that they were slower than the alternatives in a synthetic benchmark? It would be really surprising that those were the performance bottlenecks.

Re: JSC loves ES6

#18

Post by kccqzy » Mon, Jun 05, 2017, 10:54 PM UTC

pizlonator wrote: post #13

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!

Dunno about zero. Sounds hard.

I think what OP means is that instead of bundling a copy of Chromium, just use the system-provided WebKit and JSC, which is already loaded into memory.

Re: JSC loves ES6

#19

Post by avaer » Mon, Jun 05, 2017, 10:54 PM UTC

ergothus wrote: post #16

vmasto wrote: post #15

I really wish we would stop calling it ES6. Browser vendors should be especially careful to call ES2015 by its correct name and help stop perpetuating the confusion (ES6, ES7, ES2016, ES2017, you can see how this quickly gets confusing).

ES6 is 3 syllables. ES2015 is 6 or 7 (depending if you say "twenty fifteen" or "two thousand fifteen"). I'm a dev. I'm lazy. I have no particular objection to the idea of moving away from ES6 as a name, but if the new name isn't more useful, it's not going to gain any ground.

But the new name is more useful. It tells you how many years you're behind.

Re: JSC loves ES6

#20

Post by om2 » Mon, Jun 05, 2017, 10:55 PM UTC

vmasto wrote: post #15

I really wish we would stop calling it ES6. Browser vendors should be especially careful to call ES2015 by its correct name and help stop perpetuating the confusion (ES6, ES7, ES2016, ES2017, you can see how this quickly gets confusing).

We'll probably use years for the future versions. ES6/ES2015 was a much bigger change than we're expecting from the next few versions so it seemed like a good point to make the break.