Comments on: Case Study: Usable and Unusable APIs

By: mutuelle

mutuelle — Sat, 29 Aug 2009 10:45:28 +0000

I m all right with you…

By: mutuelle

mutuelle — Fri, 21 Aug 2009 11:33:45 +0000

good article,thank you

By: Marti

Marti — Wed, 29 Jul 2009 15:07:41 +0000

Sad but true

By: mutuelle

mutuelle — Tue, 28 Jul 2009 22:11:03 +0000

Thank you for this article

By: Paul W. Homer

Paul W. Homer — Mon, 27 Jul 2009 18:59:18 +0000

Somewhere along the way, the Java “aesthetic” for coding became bend towards the noisy and overcomplicated. I tend to think it’s a combination of the earlier brute force movements towards real-world objects, useless flexibility and the desire to just get it done first, and then think about it later. However it came about, it generally seems wise in most applications to cover over many of these libraries carefully, rather than to allow their pathologies to percolate upwards. If the foundation is a mess, it always demands extra effort to keep that from infecting the rest of the structure.

Paul.

By: John Doe

John Doe — Mon, 27 Jul 2009 16:41:55 +0000

People have been using dom4j and jdom for years… The only reasons for which people use JDK libraries(XML) is because:
- They don’t want to add new dependencies
- They are doing something trivial
- They already have lots of utility classes in their code base