About the time it started getting called "Java EE" instead of "J2EE" they started stripping out most of the requirements for redundant default configurations. Some of the complexity is gratuitous, sure, but a lot is because it attempts to let developers handle more complex situations or scaling requirements (horizontal and/or vertical). I used to scoff years ago at some of the layers and knobs, until I found myself needing to use them, then I thought "these guys were smart to think of this in advance".
There are worse things than having a codebase -- already somewhat sanity-checked by the compiler, mind you -- that you can drop into an application server along with a small configuration file, and it can just plug into your preferred vendor, your preferred database, your system/user/network configuration.
I've played with a lot of frameworks and written others. Regardless of hype or abstract quality (and by the way I used to really detest Java as a language; now it's down to a mild dislike as they've improved it and things like Lombok have come along) it turns out I can just sit down and get work done with it and to some extent it helps my projects be "the right way" out of the box for later growth, and I have to respect that.
On the contractor side, clients for some reason think the spec should be free and want to pay only for delivered code.
And I want a pony.
So why can't they move their feet out of the fire by verifying the public key themselves and uploading it into their own Gmail account?
No registrar can beat the verification of me pasting the public key from my own server and verifying the fingerprint out-of-band.
I have. In fact I've deployed Firefox and other Mozilla applications to tens of thousands of users. I built the configuration and packaging environment, as well as some tools for us to manage site- and role-specific autoconfigs. A coworker of mine spent a lot of time in the JavaScript autoconfigs themselves and came up with some pretty impressive automations.
I can see how you might want GPO support if you're into it but for us it was great that we could deploy variants of one single file and support all 4 major OS platforms in use within our organization. We were able to provide preview releases of new Firefox builds that hadn't yet been tested with all the corporate apps and users could switch between them. As far as locking the settings or preventing auto-update, both of those tasks were both trivial and obvious.
Honestly Firefox and the rest of the products were fine to configure. The hassles really came a bit from what you'll have trying to automate any large organization, and most especially the politics from middle managers arguing about whether we could just push the update yet. Oh, the politics.
This is the fault of game " 'UI' 'designers' " who insist on drawing their own things instead of using system widgets. At best they act like the designer's preferred platform no matter where the application is running. More likely, they only approximate the coarsest features of the thing being emulated and leave the user with a constant feeling of frustration.
Really? You have to develop your own scrollbar?
(Scrollbars are actually a good example. I should note that this idiocy is now making its way into Web "design", where thanks to the "everything should be a tablet" crowd, you start to see people making custom scrollbars that hide unless you happen to mouse over the right place, and are too thin to grab with the mouse.)
"Thank heaven for startups; without them we'd never have any advances." -- Seymour Cray