5 ms·

Isn't this why we have the W3C, so standards don't get made unless multiple people benefit? This seems like Microsoft with IE6 all over again.

ahupp 8y ago
> This seems like Microsoft with IE6 all over again. IE6 gave us XMLHttpRequest because they wanted it to build Outlook for the web. That seems like it turned out ok. In general I think building browser-specific features, seeing what works, and only then standardizing is a much better path than starting with W3C.
- news_to_me 8y ago
  No it isn't. It leads to fragmentation of the platform, and pretty soon you'll start seeing "Works best in Chrome!" tags on websites, because developers are too lazy to implement fallback solutions where <portal> (or whatever other proprietary extension) isn't supported.
  - moreira 8y ago
    I already see them all the time, but this time dressed up as “please upgrade to a modern browser. But not Firefox. Not Safari. Definitely not Edge.”
    - ddalex 8y ago
      Perhaps Edge. A recent version.
- altfredd 8y ago
  > IE6 gave us XMLHttpRequest because they wanted it to build Outlook for the web. That seems like it turned out ok. That depends on one's definition of "ok". I don't think that modern web is ok.
Ajedi32 8y ago
No, the purpose of the W3C is to make sure we don't end up with multiple slightly different, mutually incompatible variations of the same thing. It's not meant to be a gatekeeper for new features. That said, Portals _are_ going through the normal W3C process for experimental features via the Web Incubator Community Group: https://wicg.github.io/portals/ https://wicg.github.io/portals/
- username223 8y ago
  And the "standard" is written entirely by Google, and soon to be released in Chrome. The W3C and IETF are so thoroughly captured as to be little more than two small technical documentation groups at Google. It's the old Microsoft playbook, disguised at the expense of two decreasingly-credible industry standards bodies.
- AnIdiotOnTheNet 8y ago
  Wait, how many different local data storage standards are there again? I keep forgetting which ones are deprecated by which browsers. W3C is a joke. The modern web is, like the old web, run by the dominant browser vendor. Calling it an open standard is just marketing.
deleted 8y ago
[deleted]
timdorr 8y ago
Yes, and this is going through the W3C's WICG process: https://wicg.github.io/portals/ https://wicg.github.io/portals/ If you want to contribute, there's a repo full of issues that's completely public: https://github.com/WICG/portals/issues https://github.com/WICG/portals/issues

ahupp 8y ago

> This seems like Microsoft with IE6 all over again. IE6 gave us XMLHttpRequest because they wanted it to build Outlook for the web. That seems like it turned out ok. In general I think building browser-specific features, seeing what works, and only then standardizing is a much better path than starting with W3C.

news_to_me 8y ago
No it isn't. It leads to fragmentation of the platform, and pretty soon you'll start seeing "Works best in Chrome!" tags on websites, because developers are too lazy to implement fallback solutions where <portal> (or whatever other proprietary extension) isn't supported.
- moreira 8y ago
  I already see them all the time, but this time dressed up as “please upgrade to a modern browser. But not Firefox. Not Safari. Definitely not Edge.”
  - ddalex 8y ago
    Perhaps Edge. A recent version.
altfredd 8y ago
> IE6 gave us XMLHttpRequest because they wanted it to build Outlook for the web. That seems like it turned out ok. That depends on one's definition of "ok". I don't think that modern web is ok.

Ajedi32 8y ago

No, the purpose of the W3C is to make sure we don't end up with multiple slightly different, mutually incompatible variations of the same thing. It's not meant to be a gatekeeper for new features. That said, Portals _are_ going through the normal W3C process for experimental features via the Web Incubator Community Group: https://wicg.github.io/portals/ https://wicg.github.io/portals/

username223 8y ago
And the "standard" is written entirely by Google, and soon to be released in Chrome. The W3C and IETF are so thoroughly captured as to be little more than two small technical documentation groups at Google. It's the old Microsoft playbook, disguised at the expense of two decreasingly-credible industry standards bodies.
AnIdiotOnTheNet 8y ago
Wait, how many different local data storage standards are there again? I keep forgetting which ones are deprecated by which browsers. W3C is a joke. The modern web is, like the old web, run by the dominant browser vendor. Calling it an open standard is just marketing.

deleted 8y ago

[deleted]

timdorr 8y ago

Yes, and this is going through the W3C's WICG process: https://wicg.github.io/portals/ https://wicg.github.io/portals/ If you want to contribute, there's a repo full of issues that's completely public: https://github.com/WICG/portals/issues https://github.com/WICG/portals/issues