4 ms·

> Of course they haven't. Of course they haven't what? > "this is not really true" and "all chrome-only proprietary APIs were dropped" First of all, that's i

> Of course they haven't. Of course they haven't what? > "this is not really true" and "all chrome-only proprietary APIs were dropped" First of all, that's insane, but secondly, no one is even claiming the latter. It's easy to make up things all day. Say something connected to reality.

dmitriid 4y ago
> Say something connected to reality. Easy. I even gave links to show how modern web "standards" work. To quote myself: "Is this true for 100% of things that Chrome is shipping? No. But it's so asymptotically close that the difference doesn't matter. They ship 40 to 70 new web APIs in each version. That is, 40 to 70 new Web APIs every month. Over 500 new APIs a year. How many do you imagine they even pretend to be a standard?" All this with response to literally what has been happening for the past several years: Chrome ships its own non-standards (even if it spits out a spec doesn't make it a standard), developers start using them, due to Chrome dominance its now a de facto standard. To think otherwise is to be completely oblivious to what's happening in web standards. Edit. As to "then someone writes a standard". This also happens. See Web HID timeline: https://github.com/mozilla/standards-positions/issues/459#issuecomment-886271967 https://github.com/mozilla/standards-positions/issues/459#is... Same happened to WebRTC, by the way. Stable spec version was finally complete in 2018, 7 years after Chrome spat it out and called it a standard. And so on and so on.
- pwdisswordfish9 4y ago
  None of that matters. What matters is whether the standardization process "is" the process described in this comment: https://news.ycombinator.com/item?id=33989349 https://news.ycombinator.com/item?id=33989349 And the answer is, "no, that's not the standardization process", and furthermore, "that comment was hyperbole". If you can't admit this, then you are disconnected from reality. None of your words or links will make the original comment true.

dmitriid 4y ago

> Say something connected to reality. Easy. I even gave links to show how modern web "standards" work. To quote myself: "Is this true for 100% of things that Chrome is shipping? No. But it's so asymptotically close that the difference doesn't matter. They ship 40 to 70 new web APIs in each version. That is, 40 to 70 new Web APIs every month. Over 500 new APIs a year. How many do you imagine they even pretend to be a standard?" All this with response to literally what has been happening for the past several years: Chrome ships its own non-standards (even if it spits out a spec doesn't make it a standard), developers start using them, due to Chrome dominance its now a de facto standard. To think otherwise is to be completely oblivious to what's happening in web standards. Edit. As to "then someone writes a standard". This also happens. See Web HID timeline: https://github.com/mozilla/standards-positions/issues/459#issuecomment-886271967 https://github.com/mozilla/standards-positions/issues/459#is... Same happened to WebRTC, by the way. Stable spec version was finally complete in 2018, 7 years after Chrome spat it out and called it a standard. And so on and so on.

pwdisswordfish9 4y ago
None of that matters. What matters is whether the standardization process "is" the process described in this comment: https://news.ycombinator.com/item?id=33989349 https://news.ycombinator.com/item?id=33989349 And the answer is, "no, that's not the standardization process", and furthermore, "that comment was hyperbole". If you can't admit this, then you are disconnected from reality. None of your words or links will make the original comment true.