One of the advantages of NetBeans Platform development (and I supposed also of other module systems such as OSGi) is that such dependencies must be explicitly stated.
Large monolithic Swing applications tend to devolve because any public class is visible to any other class in the entire application. The isolation afforded by module systems like those found in the NetBeans Platform mean that only APIs you explicitly wish to be globally visible will be.
Since dependencies must be declared in such a system, it prevents "accidental" API design and makes it easy to locate consumers of your APIs so you can evaluate how they're really being used.
Follow
One of the advantages of NetBeans Platform development (and I supposed also of other module systems such as OSGi) is that such dependencies must be explicitly stated.
Large monolithic Swing applications tend to devolve because any public class is visible to any other class in the entire application. The isolation afforded by module systems like those found in the NetBeans Platform mean that only APIs you explicitly wish to be globally visible will be.
Since dependencies must be declared in such a system, it prevents "accidental" API design and makes it easy to locate consumers of your APIs so you can evaluate how they're really being used.
--Tom Wheeler 06:36, 24 February 2009 (CET)