Oh yeah because it’s been totally stagnant! Right guys? Oh because it reports all the telemetry by default back to Microsoft, oh shit that’s edge. Because it’s been breaking web standards and trying to make the world chrome rather than being a world player. Ah got it.
You're not getting it, the parent comment realized something I realized. Like Chrome adding API's that are unofficial or not supported whatsoever. There's also sites that "only work on Chrome" just like they once "only worked on IE".
> There's also sites that "only work on Chrome" just like they once "only worked on IE".
IMO, this is the heart of the matter. And the only evidence I've seen that Google is pushing that agenda is their "works better with Chrome" and bundling campaigns.
But even if Google didn't do that the problem of only-works-with websites would likely remain because of website makers. Supporting only one browser is cheaper. And it's likely there will always be one dominant browser.
My guess is the only way a responsible yet massively popular browser could prevent the only-works-with problem would be to drop the user agent identifiers. Long term it may even need to sometimes spoof behaviors of its competition. Of course Google being the dominant search crawler they could also use that to leverage a more standardized and interoperable web.
And Google is one of the worst. Google Hangout's replacement, Meet, is Chrome only. Can't even fake it out with headers or such, the software doesn't give you a chance.
I think this is important. In the bad old days, I always developed in Firefox. I made a point of following standards. I despised IE.
I still use Firefox as my personal browser, but some recent development I have done has been in Chrome. Mostly because Firefox is missing one critical feature for that project. It's not quite in the standard yet. It is Stage 3 with TC39[0].
Stage 3 means, "The solution is complete and no further work is possible without implementation experience, significant usage and external feedback."
So they need browsers to implement it and provide feedback. Chrome has had it since v63. Firefox has had a bug for it for more than a year, but no public progress. Node will have it next month.
I chose to move ahead on it six months ago, figuring Firefox would be on board before I was ready to release. I was wrong. But I'm not going back. Partly for the same reason I stubbornly developed in Firefox during the IE years. This one feature is all that prevents my code from working in Firefox. They will get there eventually. I will not go back to giant build frameworks and bundlers and code splitters and transpilers and gigabytes of tooling. My code works now without those. I look forward to Firefox stepping into this world. I'm eager for that to happen. In the meantime, my users can use Chrome.
There's also sites that "only work on Chrome" just like they once "only worked on IE".
Oh, no. That must be prevented. Like, if they made it so gmail and google docs only worked with Chrome, now that practically everybody has moved to gmail.... There would be no defense of such a move.
