JavaScript opens doors to browser-based attacks

TalkBack 30 of 91:: Next »; « Previous

Thread View
Flat View

Java Applets Rize: This is one reason why you should use Applets instead of AJAX and why Microsoft's recent changes in its browser upgrade is so evil. Lets review.

A decade ago the IT industry rejoiced over Java and lots of Applet controls were created. But Microsoft feared Java, this according to Judge Jackson and stated during the last Microsoft antitrust case. Hence a campaign of FUD (Fear - Uncertainty - Doubt) was begun and with it the notion that Java, contrary to its original design, was meant for servers rather than desktop units.

To further disparage Java, Microsoft at one time provided its own Java Virtual Machine (JVM) with the purpose of thuarting a write once run anywhere goal.

Java developers avoided battle by plying their skills on the server side, the dark side of computing, where you can hide from a monopolist and the monopolist can not exert monopoly power gained from having 95 percent of the desktop market.

As with all FUD there often is an element of truth and with Java on desktops speed was an issue. It was an issue first because Microsoft provided the JVM and was not interested in tweeking it for speed, but it was also an issue second because everyone a decade ago thought PCs would be multicore, like mainframes - in just a few years - and not 10 years as is the case.

In anticipation of multicore personal computers Java was designed for lots of threading in multiple cores on multiple CPUs and not for single threading on a fast and hot single CPU machine like last years desktops and laptops and Xbox.

The Rise of Java Applets (which are AJAX like and Active-X like controls sans the security issues) is going to happen owing to multicore laptops and PCs now flooding the market place. In fact Intel no longer makes single CPU archetecture. The applets - owing to threading - do not run slow as they do when a single CPU machine is pegged out.

The current media playor EU issues Microsoft has and the requirement that Microsoft ship a Windows flaver with no media player are directly related because open source media playor classes were long ago created for Java.

Consider how easy it is to write a control sound or a video clip in Java. I do not believe AJAX can match though I have been told sound, like a beep when data is entered in error (such a basic UI) is possible with work.

The real beauty of Applets is that you do not need a web server. So any home user can just put the classes on His/Her disk space and point the applet tag to them. HotMedia is a good example and if you search you will find even today home users using what use to be free HotMedia classes to present slide shows and film clips from there cameras.

The curret issue with IE, is portrayed as a security issue involving controls but my reserch has found concern only for Active-X controls and none for Applets. It is more likely that the IE changes regarding the running of an Applet inside a script are legal strategy to avoid a 580 million judgement against Microsoft for illegal taking of code from the Univerity of California at Berkeley. So now you get an unprofessional "click to activate and use this control" message on every web page with the Applet Tag coded as intended for security. The fix is to embed the Applet Tag in an unsecure script that also is a choke point for the control. In otherwords the applet runs significantly slower by bench mark tests.

Upon this rock of Java, the Church of the Future of Software Design is built.

Frank L. Mighetto CCP; Posted by: mighetto Posted on: 07/28/06 You are currently: a Guest | Members login | Terms of Use