|
|
|
| Java applets could have become important, except that, for many years,
politics arising from the "browser wars" between Netscape and
Microsoft and the "Java wars" between Sun and Microsoft made it well
nigh impossible to write reasonable Java applets that were supported by the
latest browsers of the day.
Nowadays, the situation is somewhat better, because of Sun's Java Plug-in, but the world has moved on, anyway, and Java applets are simply not very important in today's market. There has been somewhat of an increase in interest recently, but not enough to make much difference. This kind of messiness is why I tend to avoid the use of applets in a Java course. You have enough to contend with just to learn Java, without having to fight the browser! (actually browsers, plural!) Different Java VersionsAnother problem is that you might be developing code in, say, Java 6 (a.k.a. 1.6), but the browser that your client has only has Java 5 (a.k.a. 1.5) installed. This will not work, and your client will get a most mysterious error message which doesn't really make it clear what the problem is. If you're developing Java applets, you need to be cognizant of what versions of Java your clients have installed with their browser (or even whether they have it installed at all). Then you have to develop using the lowest common denominator version of Java -- not a good situation.
|
|
This page was last modified on 02 October, 2007 |