We do not want to limit the environments
where the Higgins components can run. Small devices is a target for Higgins
functionality. The idea is to minimize the footprint, where possible. Higgins
does not require an OSGI dependancy.
92 K of the Equinox bundle is better
than 900K of the OSGI jar. However, only a 3K class is needed.
My only worry is the fact that you aren't running on OSGi now may mean you will invent your own plug-in system to address modularity within Higgins (Class.forName hacks...?) if that's a use case. I've just seen cases where people have made this decision and then came back to inventing their own modularity layer instead of starting with OSGi in the first place and saving headaches.
Note that there are other OSGi frameworks that are significantly smaller than Equinox (Felix, Concierege)... OSGi's history lays with embedded and small home automation devices. Heck, it even runs on that BMW 5 series one of you may own ;P
There are just musings of an outsider though, so don't please take any offense ;)
