From the Editors: Business as usual at the JCP



Email    print   
July 1, 2008 —  (Page 1 of 2)
Ever since Sun formed the Java Community Process in 1998, other companies have complained that the Silicon Valley company excessively controls Java Specification Requests. Indeed, SD Times has covered many instances in which other companies have urged Sun to play nice and to run the JCP more democratically.

However, there’s no reason for Sun to do so. Java, after all, is Sun’s technology and a core part of its business strategy. Maintaining control over Java’s present and future is essential to Sun’s market position. The JCP is Sun’s sandbox. Other companies can join the JCP or they can create technologies that work with Java, but they do so on Sun’s terms.

Sun with Java is no different than Microsoft with .NET or Apple with the iPhone. That most, if not all, JCP staff are Sun employees should make it very clear: It’s Sun’s baby, it’s Sun’s vision and it’s Sun’s direction.

Take the latest outbreak, regarding the proposed JSR 277 Java Module System, which seeks to extend the existing Java Archive systems with a better packing scheme for applications and resources. Critics contend that there’s a perfectly good modular-deployment system already available from the OSGi Alliance and that Sun is going out of its way to ensure that JSR 277 is incompatible with OSGi.

Is that what Sun’s up to? It’s hard to know whether JSR 277 and OSGi will ultimately be incompatible. We’re not sure if JSR 277’s scheme is better or worse than OSGi—it’s too soon to tell. As for its motivation, the company claims that the development of JSR 277 will be transparent and that Sun will consider feedback from the outside world.

What’s going to happen with JSR 277? We don’t know. However, we support Sun’s right to develop specifications in the way that it sees best. The Java Community Process isn’t really a community; that was never its intent. It’s a way for Sun to encourage its partners to collaborate with it on the Sun specs. But the decision about what to put in Java ultimately lies with Sun. Let’s hope the company’s spec leads decide wisely.




Related Search Term(s): Java, mobile development, Apple, Sun

Pages 1 2 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Kik Launches an Open API to Enable Mobile Developers to Bake Instant Content Sharing Into Any App
API-powered developers like Rude Boy Games, DrinkOwl and FlyScreen can promote their apps to millions of Kik Messenger users 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