I kinda hate the focus on (well-deserved) uBo but not the whole Manifest V3 bullshit itself. It affects extensions like uBos most, for sure, and for some of it

I kinda hate the focus on (well-deserved) uBo but not the whole Manifest V3 bullshit itself. It affects extensions like uBos most, for sure, and for some of its core features it cannot even be worked around. But it also hurts the "long tail" of the extension scene badly. I have dozens of mature, not-really-need-to-frequently-update extensions that require (perhaps trivial) changes to fit Manifest V3. But god knows if the author is still around or bothered to update them. I'm sure some of them are not because I had to download the source code and install them manually. It's basically python 2 to 3 transition but for Chrome WebExt, even if you ignore the new API restriction part. --------------- On a broader note, I'm increasingly frustrated by the constant pressure on users to adapt their habits to software changes. This isn't just about Chrome or browsers in general. Every year, I find myself spending countless hours battling changes in Chrome, Firefox, Office, Windows, MacOS, not to mention various websites, just to restore functionalities or user experiences that were already there but have been altered or removed. This often involves tweaking hidden settings, using command line switches, or relying on third-party or self-made extensions and scripts. And it affects so-called 'power users' the most because they're typically the ones who use the software or service to its fullest. I consider myself someone who is open to change. For example, when they move the search button for the umpteenth time (I'm looking at you, Google Play Store), it's annoying, but I can adapt. However, the removal of a feature is something you can't simply "adapt" to. It leads to a tangible loss of productivity, and it's even more frustrating when a feature that was previously available is suddenly gone.