Sponsored Links
Java Plug-in reader poll highlights
Readers offer valuable insight on whether Java Plug-in is a viable solution for Web-based development in Java
- Feedback
- Discuss
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.
| Help us keep up on the issues crucial to Java developers. Send in your poll ideas! |
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?