Browsers have been stuck at 1.1.4 for years because MS is legally constrained by Sun from implementing any Java spec past 1.1.4. Unfortunately, this of course suits MS to a T - they'd have had to have tried much harder to justify something with the scope of .NET if a modern J2SE-compliant JVM was installed on every Windows PC.

On 5/29/2002 3:39 AM, Robert Bihlmeyer wrote:
Rick Lutowski <[EMAIL PROTECTED]> writes:


Why have browsers been stuck at 1.1 for years? Just a wild
guess, but might it have something to do with MS stopping Java support with 1.1, and also controlling 80% of the browser market?


It could also be because the perceived benefit for the user is not as big
as you think. Users *are* installing add-ons for flash and other crap.

/I/ certainly don't see the big win, but am willing to listen.
Pointers to screenshots may help convince me.


IMO, Java's real forte is client-side.


So go ahead and use it on your site. You'd better make it optional,
though -- but this is good advice for almost any web technology
(scripting, css, mathml, ...).



--
Damian Morris

Director, Quality Assurance
Gaming & Entertainment Technology

http://www.getsystems.com

Phone:  (+61) 2 9419 2000
Mobile: (+61) 412 808 307


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to