Speaking of browser wars, here's a difference between them from a developer's perspective:
I am responsible for a reasonably popular browser extension (users in the thousands, not tens of thousands) that I've had going for a few years now. I originally started on with the extension on Chrome. To publish an extension on Chrome, I had to pay $5 once, I think, and then upload a zip file. Done and done, there it is on the Chrome store.
I also put the extension up for Firefox. Very minimal code changes were required when Mozilla started supported web extensions, and I think now that's really no code changes at all. I did have to modify the manifest file. Anyway, zip, upload ... wait a few days, then receive rejections for some dumb reason, then rinse repeat a couple of times, and eventually, it's up there. No money was exchanged.
Tried to do the same for Safari. Apple wanted $99 for a developer account. This is a free extension, so easy pass. Not gonna bother. Also, Safari sucks.
This week I got it in my head that since MS was serious about Edge and Edge is supposedly not terrible, I should try it. So, first, to get the extension running on Edge, I have to install and run a piece of software from MS called the Microsoft Edge Extension Toolkit. It runs on your extension and then munges it in certain ways to make it run on Edge, adds a few files and changes the manifest. After that and some tweaking, I can load it as an unpacked extension on Edge and try it out. It mostly works, so great, I'll just upload this to the MS store, right?
Wrong. First, create a developer account. $19. Then create an "app." Plan on this taking an hour to set all the fields and go through all the forms. Then You need to upload an appx package. What's an appx package? Oh, it's a magically signed doohickey from MS. Here's the short process:
1. install node
2. install a node package called manifold js
3. run manifold to make a special xml manifest from the extension's json manifest
4. edit that manifest with some magic keys from the dev account you just created
5. create some resized icons, because MS doesn't have resize technology
6. run the manifold tool to create the package
7. you want to run that package locally to test it? Then
8. Creat a local self-signed certificate
9. convince your computer to trust it
10. sign your package with that cert
11. Oh, you need a tool called signtool that comes with Microsoft SDK
12. Install Microsoft SDK
13. try again to sign package
14. install package to you can test
OK, looks good, so let's upload that to the MS dev account and see what happens...
Reject because I don't have permissions to do an Edge extension. Please fill out this separate Edge extension permission form...
Well, that's where I am now. Waiting for who-knows-what from MS to do something so they can host my extension.
And people wonder... where are all the Edge extensions?!?!