Having written a few Eclipse plugins was already enough.
There are now some very cool things that make starting a new OSGi project a lot easier:
* Declarative Services, for simplifying Component definitions (No more editing XML)
* bnd / bndtools for building your OSGified jar (No more manually editing the Manifest)
ps: user and ex plugin developer asking
And actually it does use less resources than either InteliJ or Android Studio, while having faster builds.
But i have never seen it working properly in
PROD enterprise application.
FWIW, I have programmed for and deployed OSGi-based enterprise solutions. Karaf[0] was the container using Felix[1] most of the time (Equinox[2] being the other for a brief period). These are/were production systems, so I am curious by what you experienced as "never seen it working properly in PROD ..."And hardly used in industry beyond eclipse project.
We also wrapped OSGi in a services framework we created (and by that, I mean my boss wrote it, and then I added some features and bugfixes later), which we open-sourced.
What's really cool is that the Flow stuff from the article resembles a publish/subscribe library that we wrote and also open-sourced (under the name JFlux, even), which in turn was built on some interfaces that bear a resemblance to the Java 8 functional interfaces, except written for Java 6.