Browser wars

The history of Applets was caught up in the “Browser Wars” between Microsoft and Netscape and the political and business battles between Microsoft and Sun Microsystems. One of the problems of the early days was that of incompatibility. When developing an applet you had to test it against different web browsers and Java implementations. If you recall that one of the great promises of Java was “write once run anywhere” this was rather a severe blow. Today these issues are mainly history as the standard target for Java applets to day is the Sun Java Runtime, a way of allowing just about any browser to be enabled with exactly the same Java Runtime Environment (JRE).

When it appeared that applets might take over the web Microsoft introduced what was considered a competing technology in the form of ActiveX controls. The big criticism of activeX at the time was that it was not secure and it was possible to create a malicious activeX control that could access the users local hard disk. Also activeX controls were only available for the windows platform.

Applets are particularly suitable for any task that requires a fully featured industrial strength programming language. An example of this is anything connected with security. Javascript is inherently not suited to security based tasks because it is so easy to view the source code. Java Applets by contrast arrived in the form of binary .class files and the JRE has a built in security system that makes it difficult for a rogue applet to cause problems on a client computer. It is arguable that the Browser Wars are back since the huge success of the Mozilla Firefox browser. This success has come about even since the first draft of this text. With FireFox taking around 10% of the browser market, the increased desktop market share of Linux, and huge take up of broadband internet access, Applets are going to continue to be an important technology.

Last modified: Thursday, 24 July 2014, 2:54 PM