News for hackers. Stuff that matters.
Re:The Cost of JavaScript in 2019 by pier25 on Sunday June 30, 2019 @12:32PM (#20318997)
"Slowly" is the key word here.

How long have they been debating the Observable proposal? 4-5 years?

Re:The Cost of JavaScript in 2019 by vimslayer on Monday July 01, 2019 @10:25PM (#20331606)
I think one major issue with this is that ES basically can't break backwards compability, ever. Observables are a good example, actually. If we look at RxJS, which is sort of the inspiration behind observables I guess, we'll see that they are now at 6th major version of the library. Migration from 4th to 5th made bunch of renamings and other breaking changes, which just wouldn't work in ES. Migration to 6th includes an additional compability layer, which again would be permanent piece of bloat if it was in ES standard.

And all this while some other HNers are saying that the browsers are too complicated and its so sad that there won't ever be completely new independent browsers... :)

Re:The Cost of JavaScript in 2019 by pier25 on Tuesday July 02, 2019 @11:25AM (#20336015)
I understand it's difficult, but I'm not sure if it's worse to make a wrong (or slightly wrong) decision than not make any decision at all.
Re:The Cost of JavaScript in 2019 by hajile on Sunday June 30, 2019 @02:13PM (#20319556)
I thought Observable was dropped completely. It seems mostly unnecessary give that a Proxy can do the same thing (and much more).
Re:The Cost of JavaScript in 2019 by pier25 on Sunday June 30, 2019 @07:00PM (#20321111)
Re:The Cost of JavaScript in 2019 by hajile on Sunday June 30, 2019 @08:20PM (#20321477)
You are correct. I was thinking of Object.observe which was preached as the next big thing in JS only to finally be pulled from Chrome (around version 50 IIRC).

That said, does a native observable actually buy that much performance-wise? If not, then perhaps an addon library is better. Once a library makes it into JS, it is there forever. That's a big risk when decent libraries already exist.

Re:The Cost of JavaScript in 2019 by pier25 on Sunday June 30, 2019 @11:22PM (#20322223)
> That said, does a native observable actually buy that much performance-wise?

I don't know, but it should.

Re:The Cost of JavaScript in 2019 by minitech on Sunday June 30, 2019 @04:34PM (#20320339)
Proxies and Observables are unrelated. Maybe you’re thinking of Object.observe?