This artile mentions that java is prone to the framework approach, but I found the library approach eas prevalent until around 2005. Remember the old oreilly "

This artile mentions that java is prone to the framework approach, but I found the library approach eas prevalent until around 2005. Remember the old oreilly "java cookbook"? Java developers often used the servlet spec, then went to recipes and libraries as needed. Now, the notion of a java cookbook seems to be extinct -it's largely been replaced by spring. I actually think java's woes are largely due to the ramp up difficulties with elaborate frameworks rather than the language itself. It wasn't nearly so difficult to get started with web programming with java prior to 2005 (and I'm starting to detect a movement away from all encompassing frameworks even in java). Java will always be verbose and a bit lowish level compared to python or ruby, but I think it could be vastly simpler and easier to use. I'm encouraged by this article, and I hope it gains more traction in other languages.