Poll Results: Developers support JavaReady PC project — to a point

Do developers want PC hardware vendors and resellers to install a standard Java environment on all PCs — to help Java become ubiquitous in the marketplace? Given the outcome of this poll, the answer is Hell yes! And then some.

The JavaReady PC project is sponsored by the Java Lobby and seeks to have vendors and resellers install a standard Java Runtime Environment and/or the Java Plug-in on all new PCs. If the JavaWorld Poll is any indicator, the initiative certainly has the backing of developers: more than 9 of 10 voters feel it is worthy of their support.

“Everyone benefits if this succeeds, and I’m confident that it will,” says Rick Ross, founder and president of the Lobby.

Although support outside the developer community isn’t readily apparent, Ross breezily chalks this up to the route the Lobby is taking with the project: “We’re conducting a bottom-up strategy. We’re just acquiring support now. We’ve only talked to a few [vendors] and those few have been extremely open to it.” He added, “I wouldn’t rule out the possibility that we might surprise the world with some very big announcements on this.”

Poll details

Was it something we said? Only slightly more than 750 developers took the time to respond to this poll question. C’mon folks, we need your input!

Here’s a look at the actual voter breakdown:

• 61% said widespread adoption of a compatible, standard Java environment on all clients is critical to their success

• 31% said widespread adoption of a compatible, standard Java environment on all clients would be ideal, but they can live without it

• 4% said it makes no difference to them whether or not there is widespread adoption of a compatible, standard Java environment on all clients

• 3% said they prefer having various (potentially incompatible) Java environments on clients

• 1% were unsure, or offered an opinion different from those above

The numbers speak for themselves, right? Not necessarily. Numbers don’t always tell the whole story. That’s why we offer the comments section; we want you to elaborate on your choice. Although the overwhelming majority of readers expressed a desire to see Java become ubiquitous, a few expressed hesitation over Java’s maturity and, hence, its ability to do so now.

[Java ubiquity] only becomes feasible when there is a “standard” Java environment, and this can’t happen until Java has matured. At that time, it would be great.

Java is too immature for widespread distribution. Just read the article in this month’s JavaWorld concerning threads [“Programming Java threads in the real world”]. Java is not multiplatform enough for this suggestion.

I see a need for this once Java stabilizes. Now is too soon. Maybe in two or three years.

If and when Java VMs are reliable and the version cycling slows this might be a more attractive solution; but at present it’s not practical.

Of the wary, Ross says, “Java’s on a path to be a standard at the ISO. It’s easy for people to be naysayers; it’s much harder to take a proactive position.”

Following is a representative sample of the range of comments collected in the poll. To see all comments from this and other JavaWorld reader polls, head to our archive of past polls. And, of course, don’t forget to voice your opinion in our latest poll.

It’s critical to my success (61%):

Java is the only thing that holds back the likes of Microsoft from taking control of the Internet. Total compatibility and platform independence is a must for smaller companies to succeed in this business. Java isn’t just critical, it’s essential.

Is there really any other answer to this question? Why would you want to run clients that don’t work with one another? That’s the reason a lot of us abandoned the Mac years ago.

I feel that one Java will benefit the entire computing community — which will soon be equivalent to the entire world community. If we allow multiple Java versions to exist, and especially if we allow nonportable versions of Java to exist, we jeopardize the entire goal of Java and set back the very desirable goal of community and communication by several years.

A compatible standard Java environment reduces the cost of maintenance, which would otherwise be enormous for us. We are in the process of moving our two main mission-critical systems to an intranet-enabled Java-based platform. In fact, I would not be surprised if we have to mandate that all our customers access the new system with a specific Java environment for the initial release period.

It would be ideal, but I can live without it (31%):

Much like the effect HTTP and browsers had on the Internet, widespread Java [adoption would] enhance communication and bring accessibility of Java programs to many people whose experience of Java is currently limited to applets. Such a Java platform carries benefits to any business that is involved in any way with computers. The greatest benefits will be noticed by businesses that sell software but the businesses that use software will also gain. A solid Java platform will, therefore, stimulate creation and commerce in addition to communication.

It is not critical to my success, but it sure would make my life much easier!

As long as Java is not reliably cross-platform we can’t use it in Web-presentations (at least not cost effectively).

Trying to create a cross-platform application requires a standard. To achieve this, we must distribute a runtime environment with our application. Having a standard would alleviate and prevent pollution of user’s machines.

Having a standard Java environment on all clients would finally enable me to seriously consider writing a cross-platform app. Since both Sun and Microsoft are working hard to make “standard” Java proprietary, I will continue working as if there will be no true standard any time in the foreseeable future.

It makes no difference to me (4%):

From a the point of view of our business, Microsoft’s VM is a single universally available VM, since our software runs only on Windows 95/98/NT. The requirement to ship a different VM wouldn’t matter at all.

It always sounds so neat to have something pre-installed, but it just doesn’t work in the real world. Get a new computer and you really need to hit the Net to find new drivers for video, sound, DVD, etc. It’s the same with Java. Sun is updating this thing all the time so you’re going to have to verify versions on the machine before you install your stuff anyway. Also, this initiative is for PCs, which I assume means Windows. Java, however, is for everything, so you’ll have to have install routines for Solaris, etc., anyway. Might as well never trust what is on the machine and do it the hard way. I hate this but we seem to be very used to dealing with the slop out there.

Seems we already have that with Windows. Microsoft’s implementation is the best available.

It makes no difference to me because I know where to get Sun’s latest JVM. At this stage of the game, the JVM changes so often there is little to gain from having it pre-installed on a new computer — even if vendors expend what could be a significant effort to keep up with latest releases.

I prefer having various (potentially incompatible) Java environments on clients (3%):

Microsoft has the right idea. The J/Direct stuff is powerful, and needed on all platforms. Imagine being able to access the native API of the Mac, Solaris, etc. I understand what Sun is after, but it is a big world, and there is room for everyone.

A standard is not just a declaration, but also reflects market forces, and a certain acceptable level of performance and functionality. With this definition of a standard, the JavaReady PC project is irrelevant because we already get the “Industry Standard” runtime with the PC — namely Microsoft’s virtual machine running JDK 1.1.

It would be great to be certain that Swing or RMI-based apps could run on every machine, but there is also a place for Windows-only technology.

Other and/or Don’t know (1%):

The standard Java VM is already shipping with PCs (Microsoft’s VM). Why would you want to have a slower VM that’s not as compatible (Sun’s)?

Let’s get out of the business of delivering software platforms on PCs. Isn’t this what caused the problems Java is now solving?

Don’t even think about it until Java is much, much more grown up. Hey, it’s practically a new release each month. Sun is here to save its own butt, not “liberate” yours.