Well Firefox has switched to webextensions for security reasons and they received a lot of flak because of it. So I'd say the opposite, since Mozilla pushed this hard and still working on better support.
> there's no clean way for two extensions to really coordinate between each other
I don't think something like this should be allowed, could be abused. Instead browsers should embrace the fact that they've become operating systems inside operating systems and implement some of the most used extensions natively.
I completely agree about extensions setting sync tho, it's major pita across all browsers not just chrome.
Centralized storage is an optional but fully functional API in Chrome extensions. Many extensions simply opt not to use it for whatever reasons. (I'm not sure if the storage synchronizing also gets disabled by disabling the syncing of extensions. This should be made more clear, along with fine-grained extension synchronization.)
But yes, there needs to be some kind of solution to the install order issue of the network request API. I don't know why this hasn't been addressed yet.
All that being said, there's still so much that Chrome needs to fix when it comes to extensions. Extension updates are done in a very opaque way. Extensions that alter network requests have precedence based on their install order --- and there's no clean way for two extensions to really coordinate between each other. This means that HTTPS Everywhere and Decentraleyes and uBlock conflict with one another, and the solution might be to uninstall and reinstall them in a different order. That is clearly insanity. What happens when you login to Chrome on a new machine and your extensions are pulled in, is the install order guaranteed to match your previous machine?
There's also no centralized storage for extensions, which means that settings are generally going to be completely different between machines unless the extension implements its own syncing/backup code.
There's also no way to disable an extension on one machine without disabling it on another machine. That means that if you want an app on your Chromebook, it's gotta be on your desktop as well.
It's frustrating to use extensions on Chrome.