Do We Really Need the JCP?



Email    print   
December 15, 2004 —  (Page 1 of 2)
The two interesting pieces of news of the past few weeks are Sun’s open-sourcing of Solaris and Sun’s creating a new Java-persistence community-process group by melding together the EJB and JDO efforts. These two events play off each other in interesting ways.

My outsider view of the Java Community Process is that it doesn’t work. All the good technology that’s come out of the process was good technology when it went into the process. Someone came up with something useful, built it, deployed it in real applications, and then put the technology into JCP because it seemed so useful that it would benefit the community.

Most of the other Java-related technology that I use on a daily basis—Eclipse, Hibernate, JUnit, Log4J—started out the same way, as a tested tool that was built for real applications. The authors of these tools never saw the point in handing control over to Sun, however, and I can’t say that I blame them. Hibernate didn’t become accepted because it was built by renegades; it was just better than JDO. Even now that JDO 2.0 has played catch-up, why should I go with a JDO Hibernate clone whose APIs are essentially untested in real applications?

Once any technology becomes widely used, it sets a standard, of course. Hibernate is the standard persistence technology right now, so what’s the point of yet another JCP committee churning out what will undoubtedly be a bad standard? I might buy the notion that Hibernate could be improved or extended by the people who actually use it, but I can’t buy the notion of a competing “standard” created out of whole cloth.

Sun, of course, wants control of the “official” persistence standard, but that argument doesn’t hold much weight. It’s not as if “official” standards like EJB, SQL, HTML, JavaScript and so on have made it possible to write portable code. Either nobody follows standards—the business reasons for not doing so are too compelling—or the standards are so bloated, inconsistent and imprecise that everybody can implement a different subset and claim to be conforming. Java succeeded not because of Sun’s iron hand, but because programmers understood the issues and didn’t use the nonstandard variants.




Pages 1 2 


Share this link: http://sdt.bz/28308
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Apache resigns from JCP
Feud over the future of Java leads to the Apache Software Foundation leaving the executive committee of the JCP Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb