One of Java’s most heard flaws (verbosity) isn’t really tied to the language it is rooted in a more deeply source: it comes from the way we use it.
Quiz: Whats one of the most heard flaws of Java compared to other languages?
Bad Performance? That’s a long overhauled myth. Slow startup? OK, this can be improved… It’s verbosity, right? Right but wrong. Yes, it is one of the most mentioned flaws but is it really inherit to the language Java? Do you really think Closures, annotations or any other new introduced language feature will significantly reduce the clutter? Don’t get me wrong here: closures are a mighty construct and I like them a lot. But the source of the problem lies elsewhere: the APIs. What?! You will tell me Java has some great libraries. These are the ones that let Java stand out! I don’t talk about the functionality of the libraries here I mean the design of the API. Let me elaborate on this.
Example 1: HTML parsing/manipulation
Say you want to parse a HTML page and remove all infoboxes and add your link to a blog box:
DOMFragmentParser parser = new DOMFragmentParser();
parser.setFeature("http://xml.org/sax/features/namespaces", false);
parser.setFeature("http://cyberneko.org/html/features/balance-tags", false);
parser.setFeature("http://cyberneko.org/html/features/balance-tags/document-fragment", true);
parser.setFeature("http://cyberneko.org/html/features/scanner/ignore-specified-charset", true);
parser.setFeature("http://cyberneko.org/html/features/balance-tags/ignore-outside-content", true);
HTMLDocument document = new HTMLDocumentImpl();
DocumentFragment fragment = document.createDocumentFragment();
parser.parse(new InputSource(new StringReader(html)), fragment);
XPathFactory factory = XPathFactory.newInstance();
XPath xpath = factory.newXPath();
Node infobox = xpath.evaluate("//*/div[@class='infobox']", fragment, XPathConstants.NODE);
infobox.getParentNode().removeChild(infobox);
Node blog = xpath.evaluate("//*[@id='blog']", fragment, XPathConstants.NODE);
NodeList children = blog.getChildNodes();
for (int i = 0; i < children.getLength(); i++) {
node.remove(children.item(i));
}
blog.appendChild(/*create Elementtree*/);
What you really want to say is:
HTMLDocument document = new HTMLDocument(url);
document.at("//*/div[@class='infobox']").remove();
document.at("//*[@id='blog']").setInnerHtml("<a href='blog_url'>Blog</a>");
Much more concise, easy to read and it communicates its purpose clearly. The functionality is the same but what you need to do is vastly different.
The library behind the API should do the heavy lifting not the API's user.
Example 2: HTTP requests
Take this example of sending a post request to an URL:
HttpClient client = new HttpClient();
PostMethod post = new PostMethod(url);
for (Entry param : params.entrySet()) {
post.setParameter(param.key, param.value);
}
try {
return client.executeMethod(post);
} finally {
post.releaseConnection();
}
and compare it with:
HttpClient client = new HttpClient();
client.post(url, params);
Yes, there are cases where you want to specify additional attributes or options but mostly you just want to send some params to an URL. This is the default functionality you want to use, so why not:
Make the easy and most used cases easy,
the difficult ones not impossible to achieve.
Example 3: Swing’s JTable
So what happens when you designed for one purpose but people usually use it for another one?
The following code displays a JTable filled with attachments showing their name and additional actions:
(Disclaimer: this one makes heavy use of our internal frameworks)
JTable attachmentTable = new JTable();
TableColumnBinder<FileAttachment> tableBinding = new TableColumnBinder<FileAttachment>();
tableBinding.addColumnBinding(new StringColumnBinding<FileAttachment>("Attachments") {
@Override
public String getValueFor(FileAttachment element, int row) {
return element.getName();
}
});
tableBinding.addColumnBinding(new ActionColumnBinding<FileAttachment>("Actions") {
@Override
public IAction<?, ?>[] getValueFor(FileAttachment element, int row) {
return getActionsFor(element);
}
});
tableBinding.bindTo(attachmentTable, this.attachments);
Now think about you had to implement this using bare Swing. You need to create a TableModel which is unfortunately based on row and column indexes instead of elements, you need to write your own renderers and editors, not talking about the different listeners which need to map the passed indexes to the corresponding element.
JTable was designed as a spreadsheet like grid but most of the time people use it as a list of items. This change in use case needs a change in the API. Now indexes are not a good reference method for a cell, you want a list of elements and a column property. When the usage pattern changes you can write a new library or component or you can:
Evolve your API.
Designed to be used
So why is one API design better than another? The better ones are designed to be used. They have a clearly defined purpose: to get the task done in a simple way. Just that. They don’t want to satisfy a standard or a specification. They don’t need to open up a huge new world of configuration options or preference tweaks.
Call to action
So I argue that to make Java (or your language of choice) a better language and environment we have to design better APIs. Better designed APIs help an environment more than just another new language feature. Don’t jump on the next super duper language band wagon because it has X or Y or any other cool language feature. Improve your (API) design skills! It will help you in every language/environment you use and will use. Learning new languages is good to give you new viewpoints but don’t just flee to them.
Today, we held our second Dev Brunch for 2010. It was the first one in the new office, with some packing cases still around. The brunch had some interesting topics, most of them small and focussed. We discussed if the topics should be announced beforehands to avoid collision, but defined these collisions as enrichments rather than duplications.
Schneide Blog 