Sun Microsystems' James Gosling, widely known as the father of the Java programming language, has been as busy as ever lately. After spending much of 2002 and 2003 working on his own research project, called "Jackpot," in which he explored ways to make programming easier, in November, 2003, he became Chief Technology Officer of Sun's Developer Products group. In addition, he is a Vice President and Sun Fellow.
In his storied career, Gosling has built satellite data acquisition systems, a multiprocessor version of UNIX, plus several compilers, mail systems and window managers. He has also built a WYSIWYG text editor, a constraint-based drawing editor and a text editor called "Emacs" for UNIX systems. In his earlier days at Sun, he was lead engineer of the NeWS window system. Gosling is best known for designing the Java programming language and implementing its original compiler and virtual machine. He has also contributed to the Real-Time Specification for Java. Gosling received a B.Sc. in computer science from the University of Calgary, Canada, in 1977, and a Ph.D. in computer science from Carnegie-Mellon University in 1983. We met with him to talk about Sun's settlement with Microsoft, his work on tools, and his expectations for the 2004 JavaOne Conference.
Let me address some concerns. First of all, the settlement has not affected our Java technology strategy. We're not shifting strategy at all as a result of it -- the biggest effect is that those of us who were involved in litigation are no longer distracted by it anymore. It is true that, as part of the settlement, we signed up for Microsoft's Communications Protocol Program, but this in no way locks Sun or Sun customers into interoperating with any Microsoft system on Microsoft's strict terms. Right now, most of our interoperability is achieved through reverse engineering. We have the option, entirely at our discretion, to access Microsoft's specifications through the collaboration agreement. But before we do so, on a case-by-case basis, we will analyze the business case and the entanglements that such access implies, which are principally confidentiality and royalties.
Right now, the vast majority of the software that Sun produces has free and open specifications and we provide the implementations of a large and growing fraction of it as open source. We aren't going to slow down our involvement in the open source community. We have thus far launched no projects that will access any Microsoft specifications under the agreement -- we simply have the option to, if we decide that the benefits outweigh the costs. As I've said, we have not sold our soul. We haven't turned into mindless lap dogs overnight. We've had a lot of experience with Microsoft over the years. Also, in case anyone still believes that Rich Green "resigned in disgust," let me clear that up. Rich Green was my boss, and I can promise you that he left for entirely personal reasons that had nothing to do with the Microsoft settlement. Rich was one of the people who put this agreement together. And one reason he stayed so long was that he wanted to do the right thing for the community. The agreement was something that he could feel proud of. Few people understand how draining the litigation was. I mean, Rich, in particular, was nearly exhausted by the time-consuming legal process, as were many others. We were all bound and determined to carry it through to a successful conclusion. Now, thankfully, we're done. Java Tools
Our Java tools strategy takes two major directions. One is to make the process of software development as easy and approachable as possible for the largest number of developers. For quite a while, Java technology developers have been able to build extremely sophisticated applications, but the straight forward stuff was often more complex than it needed to be, especially when compared with Microsoft's Visual Studio, where people could slap together something rather quickly. I hasten to add that all of the Microsoft solutions have a huge problem of scale when it comes to turning them into truly enterprise-size applications.
One major thrust is ease of development. And we're excited about Java Studio Creator, which is centered around doing rapid development of applications that are based on the Web. We've tied together web access with back-end beta sources, either as databases or web services. The other major direction has been high-end sophisticated tools for people doing large-scale enterprise applications, like Java Studio Enterprise. If you look under the hood at the implementation of NetBeans, you'll find that, just like any other Java application, it is a large collection of classes. These classes can be used outside of NetBeans to provide a framework for general desktop applications. The platform APIs include extensive facilities built on top of Swing to do window, action, toolbar, and menu management. There is also an abstract file system that allows things like CVS (Concurrent Versions System) repositories and FTP sites to be viewed as file systems. There's a whole framework for wizards, and a facility for managing and storing settings. My personal favorite is the AutoUpdate module that allows applications (at the direction of users through plugin manager UI) to be extended by installing plugins, and to handle automatic updating when new versions appear. Taken together, these dramatically simplify the construction of sophisticated desktop applications. Apple a Day
Sun Tech Days in India
My personal high point was when my hosts brought out a cake and almost 3,000 people sang happy birthday to me. It was overwhelming! The 2004 JavaOne Conference
See Also
James Gosling's Weblog
James Gosling Biography James Gosling on NetBeans NetBeans NetBeans 3.6 IDE Released NetBeans 4.0 Release Plans Sun Java Studio Creator Sun Java Studio Enterprise Sun Tech Days in Hyderabad |
| |||||||||||||||||||
|
| ||||||||||||