It's going to be an interesting war to follow, but not to be in the middle of. Chrome is already nuking the current state of things by introducing sweeping chan

It's going to be an interesting war to follow, but not to be in the middle of. Chrome is already nuking the current state of things by introducing sweeping changes in Manifest V3. The one that caught the mainstream was webRequests and breaking content blockers. What's not talked about is how moving the "background" process from a long lived hidden web page to a short lived, event based service worker, breaks the actually useful cases of extensions. For our RSS extension it breaks a bunch of things, like polling for updates in feeds, removes any sort of complex persistent storage like IndexedDB, the ability to open a websocket connection for a realtime connection to backend infrastructure (if the user chooses to use our cloud syncing). Now Chrome has also made a sweeping change by hiding all extensions you install by default. Hiding away the main interface element of the extension. This breaks the "unread" count or the point of the browser action. How many users will actually understand that they need to "pin" extensions to the toolbar? How many extensions will you have installed that you forgot to remove? It's like the 90s again. All other browsers have moved to Chrome's extension system, which by no means is a standard. Firefox has explicitly said they will support content blockers in their current form, but not their stance on Manifest V3. Safari has disabled a large portion of the API's, and being just released, what's their story for MV3? Since there is no standard there is no work to keep the API's in sync. Firefox throws exceptions on parameters that Chrome supports. It's really demoralizing.