3 ms·

>As, the Verge already explained, Chrome is turning into the new IE6 (in case you wonder, that’s not a compliment). Not only is Google making some services runn

by srbby 7y ago

>As, the Verge already explained, Chrome is turning into the new IE6 (in case you wonder, that’s not a compliment). Not only is Google making some services running faster on Chrome, the browser also sends information only to Google. Did Microsoft make their services run faster on IE6? Did IE6 send information only to Microsoft?

The_rationalist 7y ago
the browser also sends information only to Google It's trivial to replace chrome by chromium tough
- Ratanay 7y ago
  The x-client-data header is also sent by Chromium.
542458 7y ago
Yeah, that’s kinda weirdly explained - IIRC MS had OS features that were only available to IE (I don’t remember whether those features were performance-related), while Google has browser features that are only available to Google properties.
pcr910303 7y ago
> Did Microsoft make their services run faster on IE6? Did IE6 send information only to Microsoft? The web is the new OS. Microsoft made use of certain private Windows APIs to win the browser war (by providing features exclusive to IE). I think it’s a pretty apt analogy.
JimDabell 7y ago
> Did Microsoft make their services run faster on IE6? Yes. Internet Explorer used to send out-of-spec TCP packets during the initial handshake that IIS would respond to also in an out of spec way. This had the effect of speeding up subsequent requests, but only in the case of IE talking to IIS.
- muststopmyths 7y ago
  I presume you are referring to this sort of thing: http://grotto11.com/blog/slash.html?+1039831658 http://grotto11.com/blog/slash.html?+1039831658 It is perfectly within spec to send data on a half-closed TCP connection, from the other end. That is exactly what the shutdown(SD_SEND) socket call is for. It signals the stack to send a FIN so that the other side can send data but knows to not expect more. They were probably implementing a version of HTTP 1.1 (before it became a formalized standard) that did not break existing clients (or servers) but speeded up theirs. BTW, I find it hard to believe IIS was sending more data after sending a FIN. Let's just say I worked in the vicinity of the Windows networking org in those days. I know it's not a popular history to believe among the SV crowd, but Microsoft in those days would bend over backwards for ISVs (Independent Software Vendors, or companies that wrote software for Windows) if they just whispered "your products are using undocumented APIs that I don't have access to". Regardless of whether that claim was true or not, they would work overtime to dispel the notion. The were just getting put under the anti-trust microscope, with a consent decree signed in 1994 and a bigger suit was obviously coming soon. Of course, when google does something similar with QUIC/SPDY, it's the second coming of Christ. Definitely not a way to boost their browser/core business. edit:typos
sys_64738 7y ago
Isn't this comment really tied to a particular version of Chrome though? Even Microsoft couldn't push later versions of IE due to IE6 domination.
est 7y ago
> Did Microsoft make their services run faster on IE6? Yes, the pillar of Web 2.0, the AJAX, was implemented in IE5.5 first with XMLHTTPReques.

by srbby 7y ago

The_rationalist 7y ago

the browser also sends information only to Google It's trivial to replace chrome by chromium tough

Ratanay 7y ago
The x-client-data header is also sent by Chromium.

542458 7y ago

Yeah, that’s kinda weirdly explained - IIRC MS had OS features that were only available to IE (I don’t remember whether those features were performance-related), while Google has browser features that are only available to Google properties.

pcr910303 7y ago

> Did Microsoft make their services run faster on IE6? Did IE6 send information only to Microsoft? The web is the new OS. Microsoft made use of certain private Windows APIs to win the browser war (by providing features exclusive to IE). I think it’s a pretty apt analogy.

JimDabell 7y ago

> Did Microsoft make their services run faster on IE6? Yes. Internet Explorer used to send out-of-spec TCP packets during the initial handshake that IIS would respond to also in an out of spec way. This had the effect of speeding up subsequent requests, but only in the case of IE talking to IIS.

muststopmyths 7y ago
I presume you are referring to this sort of thing: http://grotto11.com/blog/slash.html?+1039831658 http://grotto11.com/blog/slash.html?+1039831658 It is perfectly within spec to send data on a half-closed TCP connection, from the other end. That is exactly what the shutdown(SD_SEND) socket call is for. It signals the stack to send a FIN so that the other side can send data but knows to not expect more. They were probably implementing a version of HTTP 1.1 (before it became a formalized standard) that did not break existing clients (or servers) but speeded up theirs. BTW, I find it hard to believe IIS was sending more data after sending a FIN. Let's just say I worked in the vicinity of the Windows networking org in those days. I know it's not a popular history to believe among the SV crowd, but Microsoft in those days would bend over backwards for ISVs (Independent Software Vendors, or companies that wrote software for Windows) if they just whispered "your products are using undocumented APIs that I don't have access to". Regardless of whether that claim was true or not, they would work overtime to dispel the notion. The were just getting put under the anti-trust microscope, with a consent decree signed in 1994 and a bigger suit was obviously coming soon. Of course, when google does something similar with QUIC/SPDY, it's the second coming of Christ. Definitely not a way to boost their browser/core business. edit:typos

sys_64738 7y ago

Isn't this comment really tied to a particular version of Chrome though? Even Microsoft couldn't push later versions of IE due to IE6 domination.

est 7y ago

> Did Microsoft make their services run faster on IE6? Yes, the pillar of Web 2.0, the AJAX, was implemented in IE5.5 first with XMLHTTPReques.