🚀 go-pugleaf

Tor Iver Wilhelmsen wrote:

> kmoffat@halcyon.com (Ken Moffat) writes:
>
> > This is a problem. I guess I wonder why everyone would not jump to
> > 1.2.
>
> - Not yet stable enough.
> - Too many APIs to sort out - esp. if you've already started to use JGL
> - Applet writers will want to focus on 1.1, which the latest browsers
>   support fairly well.
>
> >Doesn't the jdc come with a plugin that makes all the new stuff
> > work with Netscape and Internet Explorer, and aren't the updates
> > enough to make it worthwhile.
>
> It works on IE and Explorer if you rewrite the HTML documents to use
> EMBED/OBJECT instead of APPLET. Opera 3.51 uses the plugin also for
> APPLET, the others will use the built-in VM. Also, the plugin doesn�t
> exist for all potentially interesting architectures.
>
> > What are the issues that would make someone not switch to 1.2?
>

0. If you are developing a product, its fine, but if you are client-driven
you cant ask them to change plug-ins/browsers every now and then. Its a
fact that end-users usually dont love technical problems/arguments.
1. I want to concentrate on development *using* JDK1.2 and not *testing*
JDK1.2. Testing JDK1.2 is the job of Sun's QA dept. (I agree that Java is
quiet young, impossible-to-fully-test-for-all-platforms arguments etc etc,
but using the whole developer community as a testbed for the development
product itself is sth I can't digest easily. There are some problems like
focus issues etc, which in my perspective should have fallen in QA's eyes
in the very first rounds of testing)
2. An anticipation that jdk 1.2.x bug fix release will be out soon and so
we can jump to it directly  ;-)

Vasu