> It sucks that we have to do that, but I can't entirely blame them for making their own products work better on their own browser.

You mean like MS for a long time did with MSIE?

Are we really back in the 90s, back to “This page works best in $one_specific_browser”?

This is not the future I was hoping for... On the flip side I can use Linux for almost anything, so i guess it’s not all bad.

> Are we really back in the 90s, back to “This page works best in $one_specific_browser”?

Do webdevs really check for Chrome AND Firefox compatibility? The devs I know consider the job done as long as their site works with Chrome.

> Do webdevs really check for Chrome AND Firefox compatibility? The devs I know consider the job done as long as their site works with Chrome.

That would technically only make them Chrome-devs.

This... is more fraught than you might guess. Really fiddly details can make things look goofy if you don't check.

Yes, because Google is a cool company, do no evil and such.

Well .. consider you are back in the 90s ... would you think in general, that this is "the future you was hoping for..."?

I was considering a future of native applications, connected via network protocols, with the browser being used for hypertext documents.

Rambox was a FOSS desktop app based on Electron to house all your Chrome apps in tabs.

Rambox went proprietary, but was forked into Hamsket. Might be easier than what you're using now.

https://github.com/TheGoddessInari/hamsket

Just like you can't blame Microsoft for making ActiveX work best on Windows.

If they did it while talking about open standards, then we would.