Computers Today, December 1-15, 1998, Master File, pg2

December 1-15, 1998 MASTERFILE

Set-top TV you Never Saw

Creating a new language was never in the agenda of Sun Microsystems' hush-hush "Green Project". The Inside story of how Java was born.

Web Runner It all started with a blunt letter.

In 1990, Sun Microsystems software engineer Patrick Naughton was fed up with trying to support the hundreds of different combinations of software APIs used within the company. When he told CEO and friend Scott McNealy of his plans to accept a job offer from NeXT, McNealy asked Naughton to create a list of his complaints and to suggest a solution "as if you were God."

When Naughton created his list, he didn't pull any punches about Sun's shortcomings. Naughton said the NeWS software architecture the company was working on should be scrapped. He suggested that of the more than one hundred people working in the Window Systems Group at that time, most of them wouldn't be needed if Sun straightened out the technical mess. After Naughton sent the letter to McNealy, he figured it would be ignored. "Why should I care?" he asked himself. "I'm leaving anyway."

Much to Naughton's surprise, the letter did make a difference. Quietly, it was E-mailed to many of Sun's top software engineers. Naughton's E-mail box was flooded with messages from colleagues who agreed with his assessment of the firm's situation. Bill Joy, one of Sun's founders, and James Gosling, Naughton's mentor at Sun, supported his views and added fuel to the fire by raising many of the same concerns to other senior executives.

The Green Project

The day Naughton was to leave for NeXT, Sun made him a counter offer. The company would create a team of top software developers and free them to do whatever they wanted. The only expected deliverable: make something cool.

The team of six, codenamed Green, went into a self-imposed exile; discussed what they liked and didn't like about the technologies that were out on the market; and took apart countless electronic devices, such as Nintendo Game Boys, TV set-top boxes and remote controls.

The reason for this free-form exploration of Nintendos and other consumer electronic devices was to find a way for the appliances to talk to each other. The Green team discovered early on that electronic devices such as video cassette recorders, laser disk players, and stereos were all made with different CPUs.

Thus, if a manufacturer wanted to add enhanced functions or features to a TV or VCR, they were stuck because they were limited by what the hardware and its wired-in programming would allow them to do. This, coupled with the fact that the chips used by many of these devices were limited in program space, suggested a fresh approach to software programming that might be a key to innovation in this product space.

Lap Top The team's efforts kicked off the development of a new object-oriented programming language that Gosling called Oak, named after the tree outside his window. Loosely based on C++, the language was stripped down to a bare minimum in order to be compatible with the limited space the chips in handheld devices would offer, and was designed to allow programmers to more easily support dynamic, changeable hardware.

The Duke Arrives

As work on Oak continued, the Green team conducted extensive research into how and why people were attracted to certain video games and how they interacted with various kinds of electronic equipment. After collecting their research data, the team developed a handheld, remote-control-like device with a tiny visual interface. The device was dubbed *7 (StarSeven), named after an "answer your phone from any extension" feature of the phone system in the Green Team office. It featured an animated character named "Duke" who helped guide users through the easy-to-use, image rich, graphical interface remote control. Central to the design of the *7 was the conviction that the interface must be engaging and fun to use, and that the device itself must be a small, personal artefact. "Duke," created by Joe Palrang, would go on to become Java's mascot.

Sun turned the Green team into a wholly-owned company called First Person. The new firm had an interesting concept but was not clear on its aims. After struggling to come up with a marketable idea, the company decided to pursue the interactive television market that seemed to be emerging.

A deal with Time-Warner to create set-top boxes fell through at the last minute. Another deal with 3DO was scrapped when that company's chief executive wanted exclusive rights to the technology. Thus First Person's foray into creating set-top boxes for video-on-demand fizzled.

The Mosaic of Java

The company's fortune changed in 1993 when the National Center for Supercomputing Applications introduced Mosaic, and the virtual Web was born. More Web technology soon followed, and the Internet, formerly a home only to scientists and educators, began to bustle with traffic.

In early 1994, the First Person team recommended focussing its limited resources on a software system for online multimedia. Bill Joy took that initiative further by positioning Oak as a "language-based operating system" and took up Naughton's suggestion to give it away in source form on the Internet. The Oak language itself became the product, instead of part of a device. Arthur van Hoff wrote an Oak compiler entirely in Oak instead of in C. Naughton and Jonathan Payne built an Oak-ready browser called "WebRunner" (after the movie Blade Runner). The first applet--Duke waving back at his parents over the Internet--was born.

Sun backed the decision to give the language away, but not before renaming it Java. Much has been made of the now famous name but consider the fact that it could have been called either Neon, Lyric, Pepper or Silk.

With Java in the hands of the Internet community at large, all that was needed was a way to run Java applets. "WebRunner" was renamed the HotJava browser because of a trademark conflict. Then, Netscape began supporting Java. Now millions are Java-ready, and Duke has never looked back.

Will Java change the way we compute, and applications run in companies and the World Wide Web? Only time will tell, but one thing is certain--it's unlikely that letters such as the one written by Patrick Naughton complaining about multiple and incompatible software APIs will ever need to be sent again.

Issue Contents Write to us Subscriptions Syndication