> Вот что им с самого начала мешало взять OSGI для модульности?
> Теперь в кровавом энтерпрайзе модульность двойная. Был JAR hell, будет classloader hell.

Surprise! В кровавом ынтырпрайзе osgi не нужен. Или у вас какой-то неправильный ынтырпрайз на жабе SE? :)

OSGi seems like an idea to keep selling new books and training, while the functional needs have been covered for eons by the JAR/EAR packaging & deployment in JEE. Those who buy into it simply never got to understand how they're being manipulated. There's also a question of trends and fashion. I.e. non-engineering considerations that are a shame to this industry.

Reinventing the wheel is profitable because there are tons of fools out there. Unfortunately, there are tons of management-type simpletons who want to be on the "bleeding edge of technology" who will gladly fund their employees' courses, absorb the learning curve, and then pay through their nose in "re-engineering" of things that had nothing wrong with them to begin with.