News for hackers. Stuff that matters.
Re:OSGi After 20 Years by finnjohnsen2 on Saturday June 08, 2019 @01:23PM (#20133665)
"Few people outside the OSGi even remotely understand the requirements and capability model, and that is their loss. However, organizations that reach the maturity level to use it will never let it go. "

I consider it a poor evangelism approach to make me feel stupid and useless. In all honesty I tried to understand OSGi about ten years ago and failed to understand how to get started and how my current project could benefit from this. So we kept using maven and eventually gradle.

Re:OSGi After 20 Years by coding123 on Saturday June 08, 2019 @01:41PM (#20133814)
It isn't really a competitor to maven or Gradle.
Re:OSGi After 20 Years by watt on Saturday June 08, 2019 @03:15PM (#20134451)
I can see how running a bunch of fat jar services each in dedicated JVM can be competitor to running loads and loads of little OSGi components in one big huge JVM.
Re:OSGi After 20 Years by h_r on Sunday June 09, 2019 @10:53PM (#20143524)
Maven and Gradle don't run anything in a dedicated JVM. They're just tools to accomplish various goals based on your dependencies: compile, package, test, maybe deploy. Not even remotely similar to runtime module management like you get in OSGi.