Java Plug-in reader poll highlights

Earlier this month, Sun officially released Java Plug-in (formerly known as project Java Activator). The plug-in lets Web app developers select Sun’s latest JVM and class libraries as the runtime environment for their Java applets by adapting their HTML code (with the bundled HTML converter) to accommodate it.

Note: The background portion of the poll originally indicated that Java Plug-in does not support non-Win32 computers when, in fact, it works with Win32, Solaris, and Linux computers. JavaWorld regrets the error.

When asked whether or not they would use the Java Plug-in in their projects, almost 3 out of 4 of 630 respondents said they would consider employing it in at least some of their projects.

That’s a pretty significant chunk of voters, and should allow Sun to feel a little satisfaction about how valuable pure Java is to the Java community.

But there is another side to the story. Concerns over the performance of Sun’s VM, quirks with the plug-in, and the concept of the plug-in itself were a few of the red flags raised by all respondents.

Many readers expressed great faith in Sun to bring its VM implementation up to snuff with Microsoft’s non-compliant, but admittedly faster VM; however, they were not as kind when it came to the plug-in itself:

The plug-in would be great if Hotspot was included and actually worked as advertised.

Why should the HTML code of a web page be modified to suit Java Plug-in?

I distribute software to the ordinary person who doesn’t understand what a plug-in is and why he should have download it.

The great virtue of Java has been its integration into the browser, giving the user immediate access to applets. The Java Plug-in cancels out that advantage.

A lone reader suggested a follow-up poll to determine how well the Java Plug-in strategy worked for developers. I’ll give it a few months, but I agree such a question would help to clarify the issue of seduction versus solution.

Here’s a look at the actual voter break down:

• 39% said they will use Java Plug-in, but only in select projects
• 33% said they will use Java Plug-in for all their Web-based development
• 18% said they will not use Java Plug-in in any projects

• 8% were unsure, or didn’t have a strong opinion

As usual, while the numbers are interesting, it’s the comments that truly help us gauge how readers feel. Here’s a sampling of reader responses. To see more, head to our archive of past polls.

I will use Java Plug-in, but only in select projects (39%):

I think Java Activator plays a fundamental role for Java’s future, because it provides web developers with a stable, pure platform they can use. Whenever activator’s performance doesn’t satisfy me, as developer, I’m free to select another VM.

Java Plug-in is the definite choice for intranet projects where Java presence in browsers can be easily controlled. On the Internet, however, it’s better to rely on built-in Java.

For all my corporate intranet development efforts, this is a perfect solution to non-conforming JVMs; however, on the Internet it still will be a hard sell. Why should a user take the time to download the Java Plug-in just for my applications?

I think this is all about choice. Finally developers have a choice when it comes to Java applet development. Now you can do it Microsoft’s way, Netscape’s way or the right way!

Activator beta didn’t work at all for us. The released version works, but applet downloads, initialization, and frame builds are at least 50 percent slower. Also, performance seems to degrade the longer it is used, which might indicate a memory leak. I think its a good idea to plug in VMs, but it must become faster!

I will use Java Plug-in for all my Web-based development (33%):

Frankly, what is important to me is that I am able to develop products that will run on as many platforms as possible. Sun can assure that its standards get followed on a given platform either by producing the JVM for that platform, or by certifying a non-Sun produced JVM. Either way is okay with me.

I’ve already deployed one Web-based development project using the Java Plug-in. I think that the Java Plug-in is terrific and long overdue.

Sun’s Java Plug-in solves the problem of writing around bugs in the VM implementation of the various browsers, as well as providing the ability to use an up-to-date VM. Netscape took months to provide Java 1.1 support, but now there’s no more need to wait. Sun’s Java Plug-in comes with all of Java’s latest technologies including JFC/Swing, an important component of a project I was involved in.

The Plug-in is great news, especially for intranet users where the issue of downloading and installing the Plug-in is easier to manage. Now you can roll out Swing, JDBC, and RMI, to your intranet users no matter what browser they have.

Although it will most likely take quite a while before it gains critical mass, I’m developing applets that require the plug-in now so that my company will be prepared. In the interim, our Web site will stand out to the pioneer users.

I will not use Java Plug-in in any projects (18%):

I see no advantage in the Java Plug-in. It relegates Java to the status of other plug-ins, which most users can’t be bothered downloading. The great virtue of Java has been its integration into the browser, giving the user immediate access to applets. The Java Plug-in cancels out that advantage. Sun should be working with the browser manufacturers to incorporate one standard JVM within each browser — but I guess that’s a naive dream.

I’m really enthusiastic about Java. I feel just the opposite about plug-ins. I don’t even run Shockwave anymore. I avoid Web sites that require plug-ins. (I also don’t run any kind of scripting.) It’s just not worth the trouble of downloading and then encoding a Web page.

Sun should focus its resources on finally, after 3 years, implementing a production quality VM and forget Microsoft for a while.

The customer wants speed. Its only the developer that wants the latest hype. It’s an easy choice.

You have got to be kidding! Why would I want to replace Microsoft’s VM with Activator? To destabilize my App and have AWT Text and graphics running at 1/3 the speed of Microsoft’s implementation? Secondly, I will not use Java products from Sun, because they trash developers who look for performance-related alternatives (like Microsoft’s VM). This heavy-handed behavior is not in the best interests of the Java community and ISV’s, so I will not work with them or their products.

Don’t know/No opinion (9%):

Hard to call on this one — I just don’t like relying on plug-ins. I am hoping Microsoft will stop messing with Java so we can settle down to a common JVM. I think its a wonderful idea, but having to modify the HTML is unfortunate.

I don’t yet know enough about it to make a decision either way, but I’m almost surely going to favor Sun over Microsoft every time, because Microsoft has proven time and time again to be untrustworthy and dishonest.

My intended mode of development is non-Web dependent, so I would not be using the plug-in. I can certainly appreciate the reasons behind it, but I’m not sure that applet developers should be able to tell me what version of Java to have installed on my machine.