One of the interesting things working with Java web apps is that the "best practices" keeps on changing. Frameworks that at one time are looked at as the shining example of doing things well turn into "old school" and clunky in a handful of years. The idea of "Enterprise" solutions get thrown out in favour of lighter, cleaner frameworks. Pattern overload gets turfed in favour of KISS. Vendor lock-in gets tossed for plugablility. Even the language is changing relatively quickly: they're on v6 beta 2 at the time of this writing and expecting to release it in the fall. There is always more to learn, better ways to do things. Status quo just means that you'll be left behind.
Java 5 didn't find a huge user base, and they are already releasing version 6. Kind of crazy don't you think?
ReplyDeleteI don't know if Java 5 didn't find a huge user base. I'm excited about using it with Websphere 6.1. I think that one of the things "holding it back" would be app servers not supporting it - so people are not writing non-portable code.
ReplyDeleteFrom what I read, I don't think that the jump from 5 to 6 will be as big as 1.4 to 5.