I've been preaching this for a while:
- Chrome is dominant line IE was.
- Chrome - like IE - doesn't care about the standards because they know developers will adapt to them.
- Chrome - like IE - is starting to fail.
Unfortunately, meanwhile Mozilla has been busy tearing apart a number of the things that made Firefox shine, especially the extension API. They've also been busy trying to destroy the massive trust many of us had in them by doing stupid things like injecting a silly ad extension and lying (IIRC) about the Pocket thing (nothing against Pocket, they just shouldn't have lied about it, many of us are looking for ways to fund FF development.)
Edit: I still use and recommend Firefox. For me it is still the best browser out there in more than one way, I just feel it could have been so much better.
Ho ho ho. You haven't even touched the worst that Android has to offer.
- The bluetooth stack. My god the bluetooth stack. A mix of absolutely awful APIs trying to disguise state machines, APIs trying to simplify GATT (but awfully failing at it), the Android lifecycle making you tear your hair out when you want any kind of long lived connection.
- Camera. Thankfully, CameraX from the AndroidX team makes it much easier. But a few years back? I'll just let Google's very own Camera2BasicFragment speak for itself. https://github.com/googlearchive/android-Camera2Basic/blob/m... . 1100 lines of basicness.
- Well, speaking of lifecycle, here's the Fragment lolcycle: http://boloorian.free.fr/_Media/complete_android_fragment_l_...
- The java.io.File API is basically gone. The reasons themselves are "good". The replacement, SAF is a horrible, slow, inconvenient API that breaks pretty much every file manager.
- Looking at the bug tracker is a whole other level of sadness. What's that, You'd need your testing library to ba able to instantiate a Fragment in an arbitrary Activity ? radio silence since 2019
You can report sites that are broken in Firefox at https://webcompat.com/. Mozilla engineers will debug the broken site and try to contact the site's developers. Firefox also ships some site-specific workarounds (such as spoofing Chrome's User-Agent string or tweaking some CSS). You can see the current list of site workarounds in Firefox's about:compat page.
I find this really interesting, and would like to hear more. I've been a Firefox ESR user for almost a decade, and apart from some breakage on some videoconferencing sites, and sometimes having to disable uBlock Origin, I've not faced an unusable site. And this is on ESR!
Chrome has been deteriorating in performance and power usage - on OSX at least, I recently switched back to Firefox because it was that bad (Safari is a step too far as I want to work on non-Apple platforms). Firefox has slipped from the mainstream and it's very obvious - so many sites I use on a daily basis have almost unusable bugs on FF (I have to hack CSS because token auth popup from my bank is broken, a game related website has half of the scrolling on the page broken, in general so many sites have broken scrolling on FF) - the situation with Chrome seems to be similar to IE.
And the small exposure I had with Android SDK I was shocked at the API design quality, poor documentation. Implementation is ridiculously inconsistent across OS versions and HW vendors - I was trying to create a WiFi management API for some industrial application that would connect to controller specific networks - Android has 2 layers of terrible and depricated API with documentation that was misleading at best, a new API that only worked on 10+ without backcompat, and the actual implementation was inconsistent across four Android devices we tested. We gave up on the project as the Matrix of features missing and hacks needed for every platform we could find was just not practical to maintain.