James Gosling isn't going anywhere

On Monday I talked about Simon Phipps, a Sun C-level officer who left Oracle for other things, signaling at the very least a difference in opinion on how things were and will be going between Phipps and his employers. (For hint of that, see the brief comment on that post that purports to be from Phipps, hinting that the full story of the Apache-Sun dispute has yet to be written.) James Gosling, on the other hand, appeared today at the ServerSide Java symposium in Las Vegas; as befitted Oracle's newly minted CTO of client software, he offered what seemed like a full-throated endorsement of Oracle's future management of the platform, though perhaps with a few off-script asides. You can find good coverage of his talk at eWeek and InfoWorld, along with a brief interview in which InfoWorld's Paul Krill ambushed Gosling in line at his hotel. Some high points of his remarks:

  • Java EE 6, though its integration of OSGi, is offering modularity that can make for easier programming. With the advent of the Web profile and of dependency injection, full-on Java EE can compete on ease of use with the Spring Framework. In particular, he claimed that "all the pain of EJBs has just gone away."

  • He also praised GlassFish as the first real Java EE 6 server, and in so doing perhaps undermined Oracle's attempts to cast it as a lower-level "departmental" server from which organizations will eventually graduate to WebLogic. Though in his interview with Krill he deferred to Oracle on its future, in his talk, he said, "People run lots of large-scale sites on it. Don't think of it as toy. It is definitely not a toy."

  • The Java Store, a project that seems to be pretty near and dear to his heart, has hit a snag when it came to properly collecting sales tax revenues nationwide, but that's been ironed out and the full store should debuting "any day now."

  • He praised JavaFX, but said that it's "not about generating Web pages, it's about building rich graphical user interfaces on the desktop." Someday maybe we'll find out what exactly it's really for, if it isn't stillborn!

One thing Gosling has very little interest in is something of importance to a great number of Java developers: the process and institutions by which the language is developed. He told Krill that the Java Community Process has "just gotten complicated" and that he didn't want anything to do with it; in his talk, he said that it bogged down engineers in discussion when they could be writing code. "You have to talk to people. For lots of folks, that's kind of a difficult thing," he said. Spoken like a hard-core engineer -- and like a man who's happy to work away at engineering problems for his new employer without making a political fuss.