>> To the OPS4J community I represent the mainstream corporate developer >> who only wants to consume OSGi but not understand it. > > A recipe for difficulties. > > Trying to use something that will lay underneath your entire system, but not > wanting to spend any time learning about it is not a good idea. If that is > truly your plan, I'd recommend not using OSGi at all, since you'll only come > away with a bad impression.
Please allow me to affirm - OSGi is not there yet for that kind of attitude to be workable. It's not such an evil idea though. When I started coding 15 years ago anyone who used any other tool than vi was typically regarded as a heretic. Now we use Eclipse and wait for stuff to turn red before we remember that we mis-spelled something, or remembered that we didn't add it to the classpath yet. OSGi is not that hard, nor is it an end in itself. We will eventually rely on tools to do much of the housekeeping for us, so we can focus on the code. My opinion - even it if I'm alone on this. Pax is already a lot closer than anything else in this regard. _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
