Please note: this text is provided as a courtesy and is not an official transcript.

J. Gage: For those of you that want to know a perennial trend, the way you reach people who say things like Ed has just said--he loves developers. If you have a comment or you're not feeling loved enough, here's how things work at Sun. It's ed.zander@sun.com. It's not anonymous, you know. The way this works is by you saying what you think should happen and getting it to Ed. Or getting it to somebody that loves you more than Ed-so let me introduce scott.mcnealy@sun.com.

applause

Scott McNealy: Wow. Gets bigger every year. It's amazing, absolutely amazing! The thing that's happened here in less than three years is pretty exciting. Yesterday was pretty exciting too, but I'll get into that in a little bit, but I was thinking back to where we were a year ago, you know, we had Dana Carvey, now you have Alan Baratz doing top ten lists.

I don't think people are even talking about ActiveX. I remember in my keynote we had the 20-minute ActiveX demo where it kind of commandeered a PC, took it over, and kind of shut it down at the end. We had the Hubbell Telescope. We had Thomas Dolby. And if you look how far we've come along, and what's happening here. It's pretty amazing.

I asked around yesterday and said: "What should I do? What should I not do?" And a lot of people said; skip the humor, just get to your content. Don't do a top ten list. So, I'm not going to do a top ten list today." Groans from the audience You want one? You want one? Well, it just so happens I have one.

laughter

But, I didn't actually have the topic until this morning and John Doerr's like, you know the....For those of you who are starting your own companies, you shouldn't be hanging out with me, you should be hanging out with Doerr. He's got all the money. He's the Klenner, Perkins, Caufield and Byers and they're doing the Java(tm) Fund. So go see him. John Doerr is the guy with a white shirt and a red tie over there pointing to front of audience looking like a venture capitalist.

I want to do something topical. What's topical? John's an investor in Amazon.com and he said this is true--now, I didn't make this up--you can blame John if this is not true. He said the top two best-selling categories on Amazon.com are Java technology and "Sex and the Single Nerd."

laughter

I'm not sure, so I said well, all right, so I'll do a top ten list that tends to take into account Java technology, sex and single nerds. So, my top ten list today is the top 10 pick-up lines overheard at the Hacker's lounge.

Number ten pick-up line overheard at the hacker's lounge, "Hi, I'm James Gosling." Sorry James.

Number nine, "Would you wear my Java Ring?"

Number eight, "Personally, I'm totally plug and play." Ooooh. Hey, they get worse let me tell you, like starting now.

laughter

Number seven, "Is there a back door to your system?" That's a security one!

laughter and groans

That was number seven, this is number six. I've got two number sixes. "How about a group grep?" Not many old UNIX hackers here I guess, huh?

Here's another number six. I couldn't throw out some of them. Number six, "Hey, want to sip some champagne near the firewall." Didn't work for me either.

groans

Number five, "Is the engine as impressive as the front end?" All right, here we go you'll like this one.

Number four pick-up line, "I'll shrink wrap my software if you want." Hey, it's the Bay Area, you know, space computing. You know that whole ... all right, all right.

Number three, "Want to get it on in the sandbox." All right, all right. Only two more.

Number two, "Anyone, any time, anywhere, on anything." Oh no, excuse me that's a White House pick-up line.

applause and laugher

And the number one pick-up line heard at the hacker's lounge is "Please?" There you have it.

So now to the serious meat. I don't know how you....He referring to Ed Zander did all this stuff already, so I'm not sure what I can talk about. I can recap a little bit about what's happened in the last few days and what's happened in the last year or so. When you go down the list and put it all together, it's amazing.

I love the stories I read in the press about momentum in Java technology waning. It's fracturing. It's flaming out. It's going south. I mean, I cannot imagine a technology that has been more underhyped. I mean, if we had said all of the things that I am going to say right now, a year ago ... If we had predicted that all of the lists of announcements and projects and capabilities were going to happen in the next 12 months, if we had said that a year ago, you'd have all thought we'd been smoking something. Right? It's just amazing when you look at it.

We talked about the Sun^SM Developer Connection^SM, the Java^TM JumpStart^TM that makes sure apps run consistently on Windows and Solaris^TM software and all other technologies. Personal Java^TM technology is now running on all the important real-time operating systems, in fact we put it on WinCE even. The Enterprise JavaBeans^TM components is up to its final specs. The JavaPC^TM software for DOS and 3.1, JavaOS^TM software for consumers. Even the judge got into the act yesterday and had to make a JavaOne^SM conference announcement. That was nice. I don't think that was purely accidental. Trust me. I think JavaBeans components, with the ability to put components on one system, is a big, big, important new step forward. And now with Enterprise JavaBeans components being able to distribute that across your coaxial and handle research management I think is another big step forward.

A lot of partners have announced: the Ericsson announcement with Personal Java technology to their wireless devices. Siemens has licensed the JavaServer^TM tool kit, the HotJava^TM Views^TM software and the Java^TM Media Framework. They're going to put that into all of their real-time communications systems like cell and web phones. Open TV is our leading European OS for set top boxes. They signed a Personal Java technology license. BEA Systems has just licensed the Java platform for their Java Enterprise environment. That's a very very large deal. The JavaEngine^TM technology has just been signed up by Samsung. Toshiba and Sun are collaborating on mobile technologies. Scientific Atlanta is putting Personal Java technology on their Explorer 2000 set top box, and Java technology on the back end for analog devices. And Explorer happens to be one of the most deployed interactive digital set top boxes in the marketplace. NCI, and the Oracle environment have Personal Java and Embedded Java technology licenses now. Ameristar Technologies, Inc. has Java-based agent technologies for online customers. Motorola is the largest Java application environment announcement to date; and with all of the microcontrollers, beepers, pagers, and cell phones that they ship, you're talking about hundreds of millions if not billions of devices over the term of the contract with Motorola that will be Java technology-enabled. Nokia has licensed JAE, JavaOS software and HotJava^TM technology. TCI is putting Personal Java on their set top box. IBM just signed a picoJava^TM license so that you can build custom Java technology- enabled hardware. MTI just signed up for Personal Java and Embedded Java, aimed for consumer devices. I could go on.

All of this is new. All of this is actually very recent. Most of this stuff has happened just in the last three months. Now, if momentum is slowing, hurt me with that sort of slowdown. That's a pretty outstanding set of issues. I don't want to rehash what you all know--I feel like I'm preaching to the choir a little bit here in terms of the features and capability. And you know why you're here. You're here because this has some very very compelling capabilities.

I talked to the Mercury NewsCenter. A great quote by the guy from IBM when they came out and visited James Gosling to go look at Java technology. Their immediate reaction was: "Oh my gosh, this is good. Bummer. Wish we had invented it." And I think that's a fairly clear statement. I think the gang that did this put in safety, which is an incredibly simplifying effort. It really does solve a lot of the issues.

Think about how much you deal with unsafe environments. How much you deal with security features in your everyday life. Just look around at the doorknobs, the locks, the cameras, the fences, the barbed wire and all the rest of it. With Java technology you can build an inherently safe environment. It takes the complexity overhead out of the system in a very significant way.

Eddie Ed Zander talked about choice. This whole concept of worrying about what is the operating system, or whose microprocessor are you using just shouldn't matter. And we are giving people the choice to build custom hardware that fits the model they want.

On scalability, smartcard to super computer; when we launched Java technology, I mean, nobody was thinking about Java Rings. Nobody was thinking about Java technology on the largest data warehouses, mainframes and super computers in the marketplace. But those are the big new and exciting environments.

Probably the most amazing feature of Java technology to me is how rich the API set has gotten in less than three years. And, you know, Microsoft's been working for about 20 years on their API sets. There aren't many applications I can think of any more that you can write in a Windows environment that you can't write in the Java environment. Well, there may be some. There may be some fringe kinds of environments or unique situations where you have to use Windows because the API set is not there in the Java programming language. But, less than three years into it I can't think of very many--I haven't seen very many.

And you see things like Intertainer and the other enterprise applications here. What has happened is the whole industry has caught up and passed Microsoft because there are a whole bunch of applications you can't write in Windows after three years. Like you can't write an application in Windows to your ring. Can you imagine how big that ring would be?

laughter

I'd need Robby to carry my hand around. And you don't run Windows in your data center. You don't run Windows apps on your mainframe on your super computer on your scaleable, reliable, available environment. And you don't want to put Windows in your consumer devices. Customers don't like to reboot.

applause

So when you look at it, it is fascinating. I'm going to talk a little bit about how we got there. We're also working on the performance components and some of the productivity enhancements. I think James did a lot of the work-and the team-just in terms of creating an environment that drives programmer productivity aggressively. So there's a lot of compelling reasons for doing Java technology.

Ed mentioned Sun.net. We don't carry our computers around with us at Sun anymore. We carry our Enigma cards, our authentication token card. And then we just borrow whatever computer is available. So, here's how we do it. We travel around the world, and we just carry this card. I'd like to bring Paul back up to walk through the Sun.net demo.

The reason I'm showing this demo is that I want you, as software developers, to think about writing applications that will work in this model. And the device doesn't have to be a computer: it could be a set top box; it could be a game machine; it could be an automobile that is Java-technology enabled--anything with a keyboard, a display, a network port and a Java virtual machine. We want you to write your applications so that they will work in this environment. So tell us how this works Paul.

Paul Aubin: Well, actually I just logged in to save a little bit of time, but with any Java SSL-enabled browser, I can access a server.

Paul proceeds to demo Sun.net, Sun Microsystems' intranet application

Scott McNealy: Okay, you go to some URL. You go to some server that's outside the Sun firewall. Now, any company can set this up for their customers, for their employees, for their partners, or for their suppliers.

Paul Aubin: I then use my Enigma card, which is my ID, my identifier. It creates the authorization for me to get in, and connects inside the firewall to another server that gives me access to all the tools I need. This is connecting to the IMAP server inside the network and lets me read my mail anywhere, any time.

Scott McNealy: So what has happened is he has set up a secure encrypted IP tunnel from here to a server just outside Sun's firewall and that reverse proxy is the only server that's allowed to talk to the inside of Sun's network. So Paul feels like he's on the intranet when he's actually out over the Internet. That's a very very safe and exciting way for people to do applications.

We are making big rules for all of our applications developments to do thin client environments. The big rule our IP organization has is that applets must be downloadable within two minutes over a 28.8K modem line or our employees just won't deal with it.

Now, maybe you need it to be even faster, and even thinner on the client environment. But that creates a different architecture. If you think about, for example the mistake that Corel made was to do a huge Java technology-based hairball office replacement for the Microsoft hairball. Well, that's not something I can download in two minutes over a 28.8K line. And it turns out I do probably only 10% of my email from my office these days. I do 90% of my email remotely from some other device, some other computer. The whole concept of a personal computer goes away.

Now, we've done this with our other applications--we also have Calendar Manager.

Paul Aubin: I can access any calendar inside Sun, and I can access the main database--I don't have to carry a phone book around. I can look up any phone number that's inside Sun. I can also access applications like Service Desk. Service Desk allows me to report problems or request something, a change. I can bring up Java technology-enabled applications, and I can view our intranet web pages. I can access all the information I need to do my job..

Scott Nealy: So our sales heads go to their customer sites, and customers ask a question; our sales people take them right to our internal web page and show them internal documentation, marketing pictures or whatever from the customer's work station. That is very impressive; and we do it safely and securely. The reason I like this demo is because it's not a demo, it's actually what we do. Any Sun Microsystems employee can show you this. It's not a demo it's a product and we are out installing it in our customer's base today.

Now, this product has a whole bunch of compelling features. It has authentication. It has user-independent devices. These devices are like telephones. When I pick up a telephone, it doesn't know who's using the telephone and it doesn't know what application or what you're going to do on that telephone. All devices are use-and application-independent.

It assumes thin pipes. Now, we all went off and thought about thin clients, but you really need to think about thin pipes. Java technology gives you the opportunity to develop an application that works over thin pipes, because you can have the back end, the servlet and the applet environment architected so that only the applet comes down over the thin pipe. You put a lot of your horsepower in the servlet environment, or in the back-end server room.

It is encrypted so that it is secure out over the network. It has verification. When the applet comes down onto-you know people aren't concerned when you download a Java applet to their work machine when a sales rep goes into the office. It has a reverse proxy access to your network, so you don't have people hacking into your network. And it protects the firewall. The applet only talks back to the server from which it came. So you don't have random server access all over the place. You have the sandbox layer, the no- virus environment. You have Write Once, Run Anywhere(tm). You're application -independent. This truly is a web-tone environment that takes advantage of all of the capability features and compelling features of the Java appliction environment. It truly is a web-tone environment.

So, Paul do you want to jump over to the next demo while you're up?

Paul Aubin: Yes, let's talk about the merging of web tone and dial tone.

Scott McNealy: All right.

Paul: This is Persona. Persona is a research project out of Sun Labs. This is a show card. This is a demonstration card. That one's a product. This is not for sale. Persona is a personal server. This is my intranet answering machine. I'm going to show you in a couple steps how it works. The first step works like a regular answering machine.

Paul proceeds to demonstrate a device that answers the phone and is able to tell the caller about voice mail, faxes and email the caller has received.

Scott McNealy: So this is what you have in your home or small business. And this would be connected into your phone line right? Just like your normal phone line.

dial tone and phone ringing

Scott McNealy: You're calling this little green box here... points to small device...

phone ringing

Paul: Yes and it's going to answer just like my regular answering machine.

Scott McNealy logs in and an electronic voice answers: "You have six voice, nine emails and two faxes." Paul: Here's where it's different though.

Notice that it told me how many emails I have and how many faxes I have; not just voice mail. I'm going to retrieve email. It's going to read the header information email to me.

Electronic voice says: "From Dave Haversham. Good luck with your trip."

Paul: It also has a user interface. I don't need to use the phone. The phone can be my internet appliance. I also have a Java technology-based GUI. You can see here the email that was just read to me is on the screen. So, I can read it from anywhere, any time. I can also take that email and I can drag it and drop it onto this fax machine and it will automatically bring up a window for me to fax it and I can then forward it to somebody. I could also forward it to a pager or another user. All simple appliance-like operations.

And it goes beyond that. It has what's called standing instructions. Say for instance you send me an email. I'm going to probably respond to that pretty quickly. But let's say I'm not at my desk. I can have your email automatically forwarded to my pager by having a standing instruction based on your name.

Scott McNealy: So this is a secure device you can attach to your network, to your phone line that is accessible to you or anybody who wants to send you a fax, send you an email, send you a voicemail and you can access this remotely from any other device, including another telephone.

Paul: You can personalize it. I mean, we call it project Persona. We talk about wanting internet appliances to be simple to use. We want this device to be as easy to use as opening your refrigerator. The average user has enough trouble hooking up their VCR and their answering machines.

So we created what we called a "stance." You program this device with a stance. For instance, I can change the user interface based on dropping a stance. I can also change the personality. You noticed before that it was a nice, pleasant voice that answered the phone. We've got a young man here who's got a voice. So, I get the drop voice.

Paul proceeds to demo how to change the voice by dragging and dropping an icon on the screen.

Scott McNealy: So, are we going to ship this product?

Paul: You have to answer that one for me.

Scott McNealy: Oh great. Actually what this does show is as a concept card, what can be done using a secure Java technology device that's attached to the network and fundamentally has no buttons. There's nothing to do. You just plug it in, turn it on and away you go and you can access it from anywhere. And we believe this is the kind of Java technology appliance that you are going to see in your home very soon. I want one. We've just got to convince Eddie to go build one for us.

Paul: I just want to give a real quick plug for the Java Ring and give people an update. This is the fractal that everyone's been building with their rings. We started yesterday when James announced it and you can see that we're 33% complete.

Scott McNealy: Only 33% of the people have actually gone up to the hacker's lounge and done the Vulcan ring meld, if you will, with the fractal.

Paul: It looks like a few of them have done it a few times because we have 81,000 points so far.

Scott McNealy: 81,000 hits already. All righty. Great. Thank you Paul.

applause

Scott McNealy: So everybody go to the hacker's lounge and log your ring into the computer. And I'd also like to while I'm up here thank Vin Prothro and Dallas Semiconductor one more time. They really went the extra mile here to get the Java Rings to the show and prepare the Java ring set up for all of you, so I really appreciate the hard work that they did.

I'd like to talk a little bit about where we're investing in Sun and what we'd like to see over the next 12 months. I certainly can't predict what's going to happen, who's going to sign up, what the momentum will be like and what the killer apps are going to be. Everybody always wants to know. I can't tell you for sure, but we're going to continue to spend like crazy on Java technology. And sometimes the analysts think we're spending like crazy on Java technology but--the Wall Street Journal--but we're going to continue to run Sun on Sun and continue to invest in the technology.

We're driving the performance issues very hard. We've heard that. We understand that. And I think the HotSpots technology is going to be a very positive step forward on that front.

Alan talked about stability. We're focused on that. We're going to keep driving stability and the quality, because this stuff is showing up in mission- critical environments very aggressively.

Brand is another area where we're investing heavily, and if we have to go to the courts to protect the coffee cup logo, we will do that--and we'll do it successfully. I know it's never fun to be dealing with a company that is driving this kind of strategy, but if we don't protect the logo, we won't give you the compatibility guarantees that you need on the platform for 100% Pure Java^TM. That's why we're doing it. We're doing it for the software developers so that they have one environment that they can write to and be very comfortable that if you see the steaming coffee cup logo it will work. That's our commitment. That's our focus. That's our drive. And that's what we're trying to get done.

You saw the focus on consumer devices in a lot of the announcements. We're driving Java technology down to the card, to the cell phone, to the ring, to wearable computing. We really do believe that the smartcard is the network attached device of choice. Or the ring is the network attached device of choice. You ought to be architecting into your products the concept of smart chips. Maybe some day when your kid's born they'll embed a Java Chip behind their ear making your kid totally programmable. laughter I don't know.

You also see us focusing in on the server side. Using Java technology on the server side is going to be where the money is, at least in the short term. There's a lot of money to be made on the server side; a lot of money spent; and a lot of challenges. And you ought to think about how you can use Enterprise JavaBeans components, JavaBeans components, and the servlet architecture to make money on the server side.

We're also committed to the model of moving the Java standard forward--the Java APIs, the Java interfaces, and the Java specifications. There's a lot of noise in the press right now about how it's not working, or there are fractures, or people are upset, or whatever. I'll tell you there is more consensus and success in this model than any other model I've ever seen.

Now there are three models out there. There's the Microsoft model which is: we'll invent it, we'll ship a product, and maybe we'll go back and document the specification later. Well, we're certainly not going to allow a clone-- it's not a collaborative ISO-like process to move the standard forward. It's been very successful for Microsoft. It's not a bad process if you own it and if you can make it happen. I mean, if you can basically monopolize the process, drive it, and get everybody to go with it, that's a great process. But it doesn't necessarily move an API forward. I would hardly say going from DOS to Win98 has been a blow away. Has anybody wowed at the great strides we've made moving from DOS to Win98. It doesn't have to move very quickly if you can own and control it.

The other model is UNIX. Now that's supposedly been a huge failure. You know, I hope the next sixteen years are as full failures as our first sixteen years that were dedicated to UNIX. But that process was very open, very collaborative, very industry-standards based. But it tended to be quite confusing and certainly threw a lot of surprises at the customers. Although, I think Windows has thrown a few surprises at the customer too. So I think it's all relative.

The new strategy we have is the open collaborative strategy. Now there are going to be people who are going to go after Java technology with clones or with different strategies. We're being very very careful to not allow subsetting of the Java programming language, and we don't want random subsetting. We've already got Java^TM Card^TM, Embedded Java, Personal Java, the full JDK^TM, and JavaBeans components and Embedded JavaBeans components. That gives you a set of APIs and environments to write to that cover the map quite nicely from smartcards to super computers.

There's going to be a lot of other companies that are going to confuse the story and subset even more, whether it's illegal or not to subset. We don't want a million subsets. We want a rational number of subsets. You don't want 80,000 characters. 26 alphabet characters is hard enough to deal with in the English language. We think it is going to be a real problem for developers to have to learn all of those and program to those environments. So we're going to be very, very careful with the Java brand to make sure that we have a rational and reasonable amount of subsetting to the Java architecture, so that you all have platforms that are high-volume, consistent, tested, compatible, and scaleable in a positive way.

There's going to be a lot of noise out there. You know, nobody's cloning Wang OS and there's a reason. And so there's going to be a lot of people creating a lot of confusion, but we're going to stay very, very committed and very consistent if we're doing our job right on the Java APIs.

Ed talked a little bit about some of the emerging trends and I would like to just finish here with--some hopes, tips or suggestions for three groups of you; for the equipment manufacturers, the content and application developers, and the CIO types out there in the audience. I'll just give each group some advice that we would offer at Sun, which we think makes sense in going forward.

For the equipment manufacturers, it's pretty simple. Whether you're building client-side devices or embedded environments, whether you're building automobiles, or any kind of client side environments: If there is a network on your equipment, put a Java virtual machine in it. It's very clear and simple. If you've got a network, take advantage of it and give yourself access to Java technology. If it has a CPU in it, put Java technology on the CPU and take advantage of all of the work that all of these developers are doing.

And if you haven't already, incorporate a smart chip reader so that Java Chips can be read. Every car ought to have a card reader in it. Every cell phone, every web phone, every game machine, every set top box--they all ought to have card readers. So that's the advice to equipment manufacturers, which is fairly simple and fairly inexpensive to implement. I was just talking to Chris Galley and he says the card reader on a cell phone is less than a dollar incremental cost. So certainly an automobile could add a card reader.

For the application and content developers, I think it's time now to say that Java technology is the default. As an engineering manager, justify to me why we shouldn't do it in Java technology, why we shouldn't do it in 100% Pure Java as opposed to why we should do it in Java technology. I really think it's time now. Inside of Sun, two years ago this August, we decided that the default was Java technology and it certainly hasn't hurt us or slowed us down. Pick your tools carefully. You'll want a tool that is dedicated and aimed at the Write Once, Run Anywhere strategy of Java technology. That's a veiled statement to say don't use Microsoft tools in case you didn't get it.

applause

There are lots of great tools from Sun and from other companies, like Borland and Symantec, and others who have tools that are dedicated and focused on giving you the Write Once, Run Anywhere promise of Java technology.

Test for 100% purity. Send your applications to Key Labs over the Net and get them tested. Even the best programmers in the world, it doesn't hurt to get your product looked at by a third party and run through the test suite filters to make sure that you've written 100% pure code.

Finally to the information executives out there I'd like to offer the advice that you ought to rewrite your information architectures, your IT architectures. There is a very simple IT architecture document that you can write. It doesn't have to be long and complicated. It's got a lot of acronyms in it, but they're actually fairly well known acronyms. Your IT architecture ought to read: TCP/IP, HTTP, HTML, ASCII, Java SQL, IIOP and CORBA. That's a mouthful for most golf majors like me. But, if you commit to that architecture, the beauty is that every computer that you have or will buy will run technology implemented to those interfaces. That's an unconditional statement. They will work. Tell me a computer that doesn't support HTML or doesn't support ASCII. Tell me one that doesn't do TCP/IP. Tell me one that doesn't do Java. They all do. That's the beauty of the architecture, it gives you absolute choice and it's web-enabled. Don't do Windows, COM, DCOM, Office, "CaptiveX," DMA, or any of those other architectures. Was that clear?

The second statement for the IP folks is: don't deploy any Java applications on your network that don't have the 100% Pure Java coffee cup logo on it. Then you know it's been tested, approved, and certified as 100% pure. That's just a rule. It doesn't go on the network unless it's got the 100% pure logo on it.

And third, for the IP folks, assume the large server, thin client, and most importantly, thin- type architecture that we showed here on Sun.net. Because your employees, your customers, your partners, your suppliers--everybody wants to be on your intranet, wants access to your capability, and you can do it in a conditional- access way. You can set people up on Sun.net and let them in to the web pages you want them to see and only the applets you want them to run. It's a beautiful way to let them in to only the places you want them on your intranet--only if you architect using the Java server-side servlet environments and thin-type, capable Java applets on the front end.

There's no reason when I'm the road that I need a 4,000-feature word processor. I don't know what to do with a 40-feature word processor. You can download a word-processing applet, or a mail applet, or a calendar applet and let people get the jobs done that they need to do on the road--no matter where they are. Maybe not everybody lives the life I do, which is that I'm never at home. But most of you aren't home right now, are you? So you want to be able to run your business remotely and take care of your business. I see you all in the lobbies of Moscone logging in over the network. Wouldn't it be great if you had access to every one of your corporate applications right there in the lobby--secure, encrypted, safe, in a Java applet available to you? All you had to carry to this conference was an Enigma card. I call it "the R login of the next century." Sun.net is the R login of the next century. Build your application environments to that.

Those are the suggestions I have for all of you this year. They will probably be a different set next year, or probably add to that set next year. I still think these will be very durable suggestions to you as you go forward.

Let me finish with a statement that John started off with: we're busy at Sun. We're going like crazy. There's lots going on. We've got the whole SPARC^TM Solaris^TM workstation and server and enterprise computing strategy. And then we've got this whole Java technology thing that just landed on us less than three years ago. I blame James and the whole crew for that. And it's been....I mean, look at this room. It's been an extra opportunity for us, creating almost insurmountable opportunities. We're not necessarily as responsive as we'd like to be.

Ed talked about our renewed focus and our renewed attitude for the software developers. I'll tell you what. We don't have the dollars. We haven't had the energy and the focus that, say, Microsoft has had on you all. And it's just a resource issue and a focus issue, and we're changing both of those. We're investing like crazy. But, I have to admit to you, the squeaky wheel is still getting its greater share of the grease at Sun Microsystems. So at the risk of getting 14,000 email messages, I encourage you if you're not getting what you need, if you need some help, if you've got a suggestion, or if you've got some ideas, send me an email message. scott.mcnealy@corp.sun.com will go directly to me. You can do sun.com and it will rattle around and get to me eventually. But just go to corp.sun.com, and I'll forward it on and I'll make sure folks follow up. The nice thing is when I forward your email with my header, it usually gets read.

laughter

So, there is an advantage to that. And I'll try and stay current on email. Although, I am out of town for 34 of the next 42 days, or something like that-- to give you an idea of why I need nomadic computing. But, we do want to support you. We do want to enlist your help in what I think is one of the great industry events of all time.

But I really appreciate all of you. The energy level here is just outstanding and I thank you. Hopefully as I'm walking around today I'll get a chance to meet as many of you as possible and exchange cards and email addresses.

Anyhow, thank you all for being here and enjoy the rest of the show.

applause