Sun's open source boss slams App Engine's Java support
Google committed a major transgression by only including support for a subset of Java classes in its App Engine development platform, according to Sun Microsystems' chief open source officer, Simon Phipps.
"Whether you agree with Sun policing it or not, Java compatibility has served us all very well for over a decade," Phipps wrote in an April 11 blog post. "That includes being sure as a developer that all core classes are present on all platforms. Creating subsets of the core classes in the Java platform was forbidden for a really good reason, and it's wanton and irresponsible to casually flaunt the rules."
Phipps also criticized Google in a Twitter post, saying the company's move "laughs in the face of a decade of compatibility."
It is unclear whether Sun will attempt to apply pressure to Google. Phipps characterized his own remarks as non-official.
"This isn't something I could comment on on Sun's behalf," he said via e-mail Monday. "My personal comments come purely from my long association with Java topics."
Sun officials could not immediately be reached Monday.
Google, which announced App Engine's Java support on April 7, has posted a list of the Java classes which App Engine applications can access.
The company might be planning to add more classes to the list, as it is calling the Java support "an early look," and has invited 10,000 developers to begin using it.
Google is also building out a page dubbed "Will it play in App Engine," a list of compatible Java tools and frameworks.
A Google spokeswoman provided the following statement in response to a request for comment: "We provide a Java 6 runtime environment in a secure sandbox. We committed to having as many standard Java tools and frameworks work with App Engine as possible, and hope to improve the product through the feedback of developers during our Early Look."
IDG News Service
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
On Twitter now
open source
Powered by Twitter
jfruh
Apple syncing patent can't come soon enough
pasmith
New Twitter features borrow from 3rd party clients
Esther Schindler
Open Source Changes the Software Acquisition Process
mikelgan
How to set up continuous podcast play on the new iTunes
David Strom
Five important Windows 7 mobility features
sjvn
Guard your Wi-Fi for your own sake
Sandra Henry-Stocker
Grepping on Whole Words
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
What?
I'm not sure what he means by compatibility. From a developer/user of the system perspective the Java support is nothing short of awesome. They made it elegant, they made it simple. They went above and beyond (way way beyond -- I did NOT expect JDO and JPA support .. wow). GWT/appengine is a killer combination. I love it. Thank you Google.Its Java-in-a-sandbox!!!
I am glad Google is putting security first by removing classes that it does not yet know how to secure. Java in a sandbox is a promising toolset - if you need full Java, use EC2.my $.02
Compatibility still matters even if you don't understand it
Ian Schumacher: That's exactly the issue. Lots of kids like you don't understand the importance of "compatibility" - which is making sure the same Java classes are present anywhere something claims to be a Java platform.It was Sun's anal fixation with "compatibility" that made Java great in the first place, put it in every company and gave you a job. It's "why should we care" attitudes like Google's that will make your job harder by ensuring every "cloud" has a different subset of Java living in it.
It's the same "we're too big to be told what to do" attitude that made mobile Java the disaster it is - every phone company demanded the freedom to make their own APIs and Sun failed to keep them all under control, with the consequence that mobile Java is a nightmare of incompatible fragments.