I've been working on an OSGi platform for the last 6 years, and I can't agree with this more.
Let's hope the JDK doesn't adopt such wrongheaded approaches, and figures out a sensible way to implement modules. If they can't, then I'd be happy with the current state of third party opt-in approaches instead.
Re:JDK 9 modules voted down by EC
by ReligiousFlames on Wednesday May 10, 2017 @01:49AM
(#14306172)
Damn straight. XML DI config files overwhelm end-users (and developers) with a metric crap container port of details and things to break in non-obvious, diffusely (un)documented ways. (See also: configuring Atlassian on-prem products)
Simplicity -> usability && maintainability && security && popularity
What has J2EE/Java EE been replaced with?
No single thing, rather it's been displaced by using specific targeted libraries instead of enormous frameworks.
Ah, thanks very much for your reply.
Having just implemented a plugin solution using it I can safely say that in the past 20+ years of software development it is the most awful technology I've ever seen. The complexity and over engineering is simply breath taking. It is worse than EJB 1.0, worse than the crazy abuses I have seen with Spring and DI, worse than than dark days of J2EE.
I have lost a lot of respect for Red Hat and IBM after this.