WebSocketStream API

https://developer.chrome.com/docs/capabilities/web-apis/websocketstream

by begoon • 2 years ago

18 7 2 years ago

developer.chrome.com

paulddraper• 2 years ago

Backpressure for a networking API.

Only took 10(?) years!

Web innovation.

ranger_danger• 2 years ago

Wrong!

How professional.

chomp• 2 years ago

This doesn't look like it's part of any sort of standard, I'm assuming this is another case of Google channeling their inner Internet Explorer.

darklion2• 2 years ago

While Chrome _does_ respect existing standards, sometimes to the point of pedantry, it also happily rolls out designed-for-our-needs web technologies and APIs into its majority-share browser immediately, only starting the standards process once it has the feature implemented. That means for months, or years, Chrome essentially has a proprietary set of extensions and APIs while its competitors are waiting for the standards process to work.

Does “having a proprietary, not-a-standard set of extensions and APIs that work only in that one browser” sound familiar? Chrome may not be dragging its feet on existing standards, but it’s so far out over the skis of where the standards are at.

THAT is what people mean when they say “Chrome is the new IE”.

pcthrowaway2• 2 years ago

In this case, it seems like it's something for which no standard yet exists that can also be polyfilled pretty easily, I see this as a good thing.

Chrome is free to release custom APIs that move the needle on eventual standardization. I only see this as a problem if they release something that can't be polyfilled.

WebSocketStream API

Related Stories