Java founder James Gosling quits Oracle

 

Father of Java now looking for a job.

James Gosling, considered by most to be the father of the Java programming language, has announced that he no longer works for Oracle.

Gosling's unexpected departure follows that of Sun chairman Scott McNealy in January and Jonathan Schwartz a month later, and backs up reports that the old guard at Sun are having trouble fitting into the new regime.

Gosling refused to explain his sudden departure at this time. "Yes, indeed, the rumours are true. I resigned from Oracle a week ago (April 2nd)," said Gosling in his blog.

"As to why I left, it's difficult to answer. Just about anything I could say that would be accurate and honest would do more harm than good.

"The hardest part is no longer being with all the great people I've had the privilege to work with over the years. I don't know what I'm going to do next, other than take some time off before I start job hunting."

Gosling apologised to TechDays attendees in St Petersburg, where he had been due to appear on Thursday, saying that he hated not being there.

Gosling joined Sun in 1984 and invented the original Java code, virtual machine and compiler. He was hugely popular at Sun and among developers, and the loss will be keenly felt and will heighten concerns about Oracle's commitment to Java and open-source coding.

Copyright ©v3.co.uk


Java founder James Gosling quits Oracle
 
 
 
Top Stories
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
ANZ looks to life beyond the transaction
If digital disruptors think an online payments startup could rock the big four, they’ve missed the point of why people use banks, says Patrick Maes.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  27%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1128

Vote