Article View: borland.public.jbuilder.java.language
Article #18099Re: Am I missing something?
From: Richard Wilkman
Date: Wed, 19 Aug 1998 00:00
Date: Wed, 19 Aug 1998 00:00
61 lines
3383 bytes
3383 bytes
Eric: MS won't play ball and NS wants out of the VM business. Don't expect the browsers to somehow catch up (and even if they did, you still can't force end users to upgrade). The only hope for those who *must* write Applets lies with the Plug-In -- or writing only 1.02 code. -Rich Eric J. Schwarzenbach wrote: > > Jordan does have a point, though it is clearly a fault of the browsers, not Java. > Their failure to support JDK 1.1 is a serious limiting factor in Java becoming a > serious development option. JDK 1.0 is too immature, and 1.1 has been out how > long?--cripes we're working with 1.2 betas already. I wince everytime I hear a > developer say, oh I'd better stick to 1.0. > > The practical browser lock-in of Java versions at such an immature phase of the > language's development is really holding the acceptance of Java as a serious > development option back. The language is getting there but people aren't seeing > it, because the browsers are forcing most applets to be build for old versions of > the technology. If we want a future with this language, let's hope the browser > vendors get with the program, and that Sun's Java plug-in takes off. > > Microsoft clearly doesn't want to cooperate and Andreeson's recent comments about > client side Java aren't very encouraging either. > > John Niesz wrote: > > > their browsers are simply too old. MS and Netscape can't keep up with Sun > > (although Sun itself is slow in updating Java). For JDK 1.1 I think the user > > needs Navigator 4.0 or IE 4.0 or better. Right now it's safest to stick with > > JDK 1.0 until everyone has upgraded their browsers. > > > > Good luck! > > > > news/earthlink.net wrote: > > > > > Ever since I have employed Java 1.1 as a language for my web page, I have > > > been getting negative feedback from customers that claim that my web page > > > causes their browser to crash. I have since discovered that their browser > > > are not capable of handling Java 1.1. Needless to say I have reverted back > > > to Java 1.0 to avoid the bad vibes I was getting from my client. > > > > > > It is plain that this attribute of Java 1.1 will spell the end of Java as a > > > programing language for the WEB. Too bad, Java added a lot to the web. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rich Wilkman Senior Quality Assurance Engineer Borland JBuilder Team If you see something that looks like an opinion up there, it's mine and mine alone. Mail sent to me from the newsgroups won't bounce but will be ignored. If I have time, I'll respond, but you have a better chance if you confine your posts to the newsgroups =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Technical Details
Message-ID:
<35DB5275.A4A55745@inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<6qfp8d$dvr$1@fir.prod.itd.earthlink.net> <35CFCAA6.1215ECB5@worldnet.att.net> <35DAFCE5.5FEA1A69@ici.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,2fc084513d39cf52 X-Google-Attributes: gidf74b3,public From: Richard Wilkman <rwilkman@inprise.com> Subject: Re: Am I missing something? Date: 1998/08/19 Message-ID: <35DB5275.A4A55745@inprise.com> X-Deja-AN: 382793924 Content-Transfer-Encoding: 7bit References: <6qfp8d$dvr$1@fir.prod.itd.earthlink.net> <35CFCAA6.1215ECB5@worldnet.att.net> <35DAFCE5.5FEA1A69@ici.net> Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.java.language