Java vs. Plugins (was RE: The Final Word On HTML (fwd))

Walter Ian Kaye (walter@natural-innovations.com)
Wed, 25 Sep 1996 22:12:44 -0700


Message-Id: <v03007810ae6fc0a02d4e@[205.149.180.135]>
In-Reply-To: <199609260323.UAA10945@server.livingston.com>
Date: Wed, 25 Sep 1996 22:12:44 -0700
To: MegaZone <megazone@livingston.com>, www-html@w3.org
From: Walter Ian Kaye <walter@natural-innovations.com>
Subject: Java vs. Plugins (was RE: The Final Word On HTML (fwd))

At 8:23p -0700 09/25/96, MegaZone wrote:

>What *should* be encouraged is the use of Java and other portable systems
>to do what plugins do today.  The problem with plugins is not that users
>need to get them - which is being solved with auto-download coming from both
>NS and MS - but that you need to write a plugin not for a browser but for
>a browser and platform combination.  I can't use 90%+ of plugins because I
>use SunOS and most of them are for Windows.  If the same functionality was
>done in Java, it would be portable.  Then the task is just to develop a Java
>engine for each platform - a lot simpler than a plugin for each platform.


I have often wondered what criteria developers use when deciding whether to
implement as a plugin or as a Java applet. Are there specific things one can
do in a plugin which cannot be done in a Java applet?

__________________________________________________________________________
    Walter Ian Kaye <boo@best.com>     Programmer - Excel, AppleScript,
          Mountain View, CA                         ProTERM, FoxPro, HTML
 http://www.natural-innovations.com/     Musician - Guitarist, Songwriter