5 ms·

These things are being slowly worked on: https://github.com/WICG/display-locking https://github.com/WICG/display-locking https://github.com/tc39/proposal-java

by snek 7y ago

These things are being slowly worked on: https://github.com/WICG/display-locking https://github.com/WICG/display-locking https://github.com/tc39/proposal-javascript-standard-library/ https://github.com/tc39/proposal-javascript-standard-library... (https://developers.google.com/web/updates/2019/03/kv-storage https://developers.google.com/web/updates/2019/03/kv-storage) https://github.com/tc39/proposal-observable https://github.com/tc39/proposal-observable ...etc

pier25 7y ago
"Slowly" is the key word here. How long have they been debating the Observable proposal? 4-5 years?
- hajile 7y ago
  I thought Observable was dropped completely. It seems mostly unnecessary give that a Proxy can do the same thing (and much more).
  - minitech 7y ago
    Proxies and Observables are unrelated. Maybe you’re thinking of Object.observe?
  - pier25 7y ago
    https://tc39.es/proposal-observable/ https://tc39.es/proposal-observable/ It's (still) on Stage 1: https://github.com/tc39/proposals/blob/master/stage-1-proposals.md https://github.com/tc39/proposals/blob/master/stage-1-propos...
    - hajile 7y ago
      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.
      - pier25 7y ago
        > That said, does a native observable actually buy that much performance-wise? I don't know, but it should.
- vimslayer 7y ago
  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... :)
  - pier25 7y ago
    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.

by snek 7y ago

pier25 7y ago

"Slowly" is the key word here. How long have they been debating the Observable proposal? 4-5 years?

hajile 7y ago
I thought Observable was dropped completely. It seems mostly unnecessary give that a Proxy can do the same thing (and much more).
- minitech 7y ago
  Proxies and Observables are unrelated. Maybe you’re thinking of Object.observe?
- pier25 7y ago
  https://tc39.es/proposal-observable/ https://tc39.es/proposal-observable/ It's (still) on Stage 1: https://github.com/tc39/proposals/blob/master/stage-1-proposals.md https://github.com/tc39/proposals/blob/master/stage-1-propos...
  - hajile 7y ago
    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.
    - pier25 7y ago
      > That said, does a native observable actually buy that much performance-wise? I don't know, but it should.
vimslayer 7y ago
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... :)
- pier25 7y ago
  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.