Tuesday, 21 August 2007

4 things I read more recently (about Java)

This is a my usual regular post on links around the web I've been reading, this time posts specifically related to Java that may interest those in the Oracle Java and JDeveloper arenas:

  • Get to know Java EE 5 - the last few months has seen the publication of some good "new features" Java posts, including this one from Roland Barcia at IBM that specifically looks at JEE. Articles like these are good for those who don't have time to read the huge array of publications but would like to keep up to date in a concise form. Obviously being from IBM this article has a Websphere focus but looking further afield to see what others are doing can provide some valuable information.
  • Java EE 6 wishlist part 2 and part 3 - the wheel never stops turning and JSR 316 has been approved for the development of JEE 6.0 specification. Already the Hibernate Team have jumped forwards for suggestions on improvements and issues to be addressed from J2EE 5.0 and earlier. These discussions I find interesting because I find my learning of JEE is fairly boxed in by the Oracle world and others sources can provide useful insight into what needs to be improved in the technology I use -- either that or I just like reading stuff and not doing any work. I linked to part 1 in a previous post.
  • Why do people insist on doing EVERYTHING in Java? - I've encountered sites where I have to ask why are we using Java? -- where the only serious answer seems to be we're using Java because Java is Java. Huh? Anyway, Gregory Pierce has started a bit of a barney on why some sites insist on doing all development in Java. Your opinions may vary.....
  • JUGs Offer More Than Free Pizza - okay, Jason Lee's post here could equally apply to any technical user group including Oracle User Groups. Given my own background as an Oracle Ace Director which was greatly facilitated by my committee participation in the Australian Oracle User Group, Jason's words ring true here for me, Java User Group or not. Forget all that Web 2.0 social website belavar, head out to your local user group meeting and meet some real people.


Robert Vollman said...

I've been frustrated by many people who believe everything should be done in Java. The end result is frequently the same: slow apps with massive memory footprints.

The most common REAL reason people use Java is because Java programmers are so easy to find. Go ahead, on your way home, shake a tree and watch three Java programmers fall out.

I plead to software vendors out there: please find at least one database professional for your team, if you're building a database app. Please. At least 1. S/he will help your Java programmers avoid at least the most egregious of design errors.

Chris Muir said...

Fair comment regards cherry picking Java programmers Robert, though I guess mileage may vary depending on what part of the world you're in. Locally (Perth - Australia) I'm struggling to find any Java programmers what so ever (slight exaggeration), but the large amount of Oracle programmers still seem to hold Java in awe (bow to the Java god -- it shall be your savior -- even though you refuse to learn it).

Your comment about database expertise within a Java team is a valid one and quoted many times by other database experts.



Osman said...

"The most common REAL reason
people use Java is because Java programmers are so easy to find."

In Fact it is hard to find a java programmer, but it is easy to find one, who says i know java.

Should we feel the difference?
Why Java Apps Slow?

Two answers seem strictly related..