Seamonkey theme
![seamonkey theme seamonkey theme](https://images-na.ssl-images-amazon.com/images/I/41wSBJ5etxL.jpg)
I am going to write up some extremely long-winded rant in blog form at some point before the FF57 release materializes, but suffice it to say, most developers that I know who have been involved with Mozilla since the Netscape days (and also those who build most of the add-ons/products that I care about, such as SeaMonkey) have shown nothing but disappointment at Mozilla's reckless plan for the Firefox 57 release. Multiprocess was rolled out in Firefox 48, on the 2nd August 2016. Then we'd have to start over at 0 extensions twice.
![seamonkey theme seamonkey theme](https://www.nda-toys.com/images/wholesale/sea-monkeys-ocean-zoo-wholesale-53581.jpg)
Those are why it would have just as well been really disruptive to space out multiprocess and WebExtensions by a few years. They wanted extension authors to be able to just directly port to WebExtensions.Īnd I do think that a lot more extension authors would have probably abandoned their projects, if they had just ported to multiprocess and then had to port to WebExtensions.Īlso, a lot of extensions sort of just continue to function without active maintenance. They had to sort of rush it, because they wanted to rush out multiprocess, to stop the bleeding of users (which has very much worked ).Īnd then they needed to follow up with the switch to WebExtensions relatively quickly, so that extension authors wouldn't start porting their extensions to multiprocess and then after that effort have to rewrite their extensions to be WebExtensions-compatible.