I'm currently working again a bit in Java, primarily because I'm currently testing out how to implement a neat extension also in the Android
App target of CopperCube
. And it is always frustrating when working with new Java APIs. Not sure why, but Java API developers seem to want to put as many Interfaces, Classes and Factories into there, to make their library look fancy. And they seem to forget that the documenting and example writing part is usually the most important part when creating a library to be used by others. If your library is there for doing one thing, then don't create 50 packages and 250 classes for it, without telling me how the hell I'm going to use that. I now tried 5 different ways to achieve what I wanted to, but it seems that it still doesn't work. Sometimes, the simpler the interface to a library is, the better it is.