7 ms·

Putting in place an infrastructure to test this kind on changes on the 5-10 most popular browser would be, I think, very cheap for a company like Google. I can'

Putting in place an infrastructure to test this kind on changes on the 5-10 most popular browser would be, I think, very cheap for a company like Google. I can't help thinking these may be deliberate moves to eat the little market shares of Chrome concurrents. I remember reading here on HN an article written by an ex-Mozilla insider relating the dissonance between the "friendly" Mozilla-Google employees exchanges and the year-long track record of very oddly recurrent "unfortunate mistakes" from Google degrading the Firefox compatibility.

acdha 5y ago
Yes - they clearly don’t test the GCP console in Firefox since they “accidentally” break it on a regular basis, and there’s just no excuse for that happening at such a rich, well-staffed company.
loulouxiv 5y ago
I am trying to find the link, but for the moment I only find comment making, I think, references to it : https://news.ycombinator.com/item?id=19815348 https://news.ycombinator.com/item?id=19815348 https://news.ycombinator.com/item?id=28495546 https://news.ycombinator.com/item?id=28495546 Does anybody here remember enough keywords to find it out ? Edit: I guess it was this Twitter thread https://mobile.twitter.com/johnath/status/1116871231792455686 https://mobile.twitter.com/johnath/status/111687123179245568... Edit 2: The associated HN thread https://news.ycombinator.com/item?id=19662852 https://news.ycombinator.com/item?id=19662852
deleted 5y ago
[deleted]
magicalist 5y ago
> Putting in place an infrastructure to test this kind on changes on the 5-10 most popular browser would be, I think, very cheap for a company like Google. The problem wasn't some web server, it's the Firefox backend services running on GCP.
marcan_42 5y ago
Testing wouldn't have revealed anything because this didn't break with Firefox outright, it only broke when Firefox telemetry used it due to a complex series of circumstances.

acdha 5y ago

Yes - they clearly don’t test the GCP console in Firefox since they “accidentally” break it on a regular basis, and there’s just no excuse for that happening at such a rich, well-staffed company.

loulouxiv 5y ago

I am trying to find the link, but for the moment I only find comment making, I think, references to it : https://news.ycombinator.com/item?id=19815348 https://news.ycombinator.com/item?id=19815348 https://news.ycombinator.com/item?id=28495546 https://news.ycombinator.com/item?id=28495546 Does anybody here remember enough keywords to find it out ? Edit: I guess it was this Twitter thread https://mobile.twitter.com/johnath/status/1116871231792455686 https://mobile.twitter.com/johnath/status/111687123179245568... Edit 2: The associated HN thread https://news.ycombinator.com/item?id=19662852 https://news.ycombinator.com/item?id=19662852

deleted 5y ago

[deleted]

magicalist 5y ago

> Putting in place an infrastructure to test this kind on changes on the 5-10 most popular browser would be, I think, very cheap for a company like Google. The problem wasn't some web server, it's the Firefox backend services running on GCP.

marcan_42 5y ago

Testing wouldn't have revealed anything because this didn't break with Firefox outright, it only broke when Firefox telemetry used it due to a complex series of circumstances.