That kind of crippling grasp on the ecosystem is difficult to tolerate, and simply nothing compared to what's going on with Google. Today on iPhone, even if you pay $100/year to be able to run unsigned code, you can't get a copy of Firefox running, because nobody maintains the port. most web developers) to continue taking browser diversity seriously. It's one of the last vectors forcing lazy web developers (i.e. The fact that Safari on iOS isn't bleeding edge is actually an under-appreciated gift to people who choose to/are forced to run older software.
CHROME REMOTE DESKTOP CURTAIN MODE UPGRADE
While one might complain about the inconvenience of supporting the few gaps in Safari on iOS, this complaint is actually of having to support people who don't (or can't) run the latest software because they (for example) haven't chosen to pay money to upgrade their computing device to something which supports Windows 10 or a recent release of MacOS.
It shouldn't be necessary to be using a bleeding edge version of Google Chrome (or its clones) in order to have a first class web browsing experience. The web should be resilient to clients which don't support all of the latest features. I don't disagree that support for open codecs should be more of a priority for Apple/Safari/WebKit. It's a bad set of changes as implemented in chromium right now. My opinion after porting several large extension projects to the space is. Overall - my first impression of the manifest v3 upgrade was fairly neutral (it's not really solving any of my pain points, and it requires a lot of changes to support - but it seemed functional).
everything from docs that are wrong, to serious issues like a service worker not activating on simple, basic, required events (like, which is literally about as basic as it gets for extensions). I'm also not thrilled at manifest v3, although for very different reasons than the adblocking limitations - I do lots of extension development, and I think the service worker approach taken is a bad mistake, forcing a distributed consensus model onto extensions without understanding the limitations that model imposes given how often extensions span multiple js contexts (across tabs/frames/content_scripts/windows/etc).įrankly - the environment is also still riddled with bugs. Those who care about this are already on Firefox, and frankly - Firefox isn't going to be the answer here (to be clear, this is opinion). I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox. I approve (of both the release and the name).
0 kommentar(er)
