Wednesday, January 23, 2013

Coupling and Modularity

There's a very good reason why I think the guy who invented Java should be shot and buried where the sun don't shine.

Going through the jwebsocket package, it's a classic representation of (wrong)Java practices -- endless imports which themselves also contain other imports. The classes in the packages are so tightly coupled that changing one line, would literally bring the whole deck of cards stumbling down.

That said, It's high time that I started breaking apart the whole thing. Focus will be on modular, highly portable stand-alone classes. Coupling will be brought to a minimum in an effort to make functions more independent.

No comments:

Post a Comment