i have used OSGI in projects and find it useful to see bundles states, Camel routes/endpoints, lot's of other useful stuff.
But i have never seen it working properly in PROD enterprise application.
Sadly my eclipse is just confirming that from time to time with errors :(
Android Studio's minimum-resource-usage-for-sane-performance is enormous. It does some things nicer than Eclipse, but there are definitely times I miss Eclipse's lean-ness, which is not a thing I would have expected myself to ever feel prior to AS.
It's big and slow, agreed, but it is very powerful. I don't know the details of the virtual FS layer but I can sympathise because that's very difficult to get right in a cross-platform way.
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 ..."
I used to work for a robotics company that made heavy use of OSGi.
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.
I don't think that this is true: OpenHAB, Nexus 3, a lot of the enterprise application servers... One can probably compile a pretty long list of things "running in production" using OSGi.