Last updated on 2012-12-10
Object orientation has given us great things, but lately I have felt that we are having great problems managing the highly coupled components that OO has created. I regularly search the web when I need code that does something, but the problem is that the functionality comes wrapped inside class libraries with complex internal relations and other classes, most of which I usually don’t need, but have to learn and understand to use the class I want. And this is a waste off my time.
It made me very glad to see that I am not the only one who feels this way. OSGi Alliance Blog: What to Depend On, extends on this idea in a very clear way, much better than I can. Enjoy.