Java Myths- Fact versus Fiction
Inside Java :There are so many myths about Java. This month, I'll look at some of the more persistent ones, and try to dispel any doubt.
Java myths - fact versus fiction
Applets can read your hard-drive, and delete files
Any attempt by an applet to access local files will throw a SecurityException. If uncaught, the applet will crash, but no file access will occur.
Java requires a web browser. Java only runs in a web browser.
Java code comes in many forms. The most familiar to users is the applet, which runs inside a web browser. However, this is only the tip of the iceberg.
Java is a hundred times slower than C, so you shouldn't ever use it for "serious" programming.
The original Java Virtual Machines were slow, so slow that a comparable C application was about twenty times faster. The gap between C/C++ and Java is growing smaller though, thanks to better designed JVMs, and Just-In-Time (JIT) compilers that convert bytecode to native machine code at runtime.
There's no point learning any language other than Java - it will dominate the software industry and put C++ programmers out of work.
There are many languages suited to very narrow and specific tasks (such as artificial intelligence) that Java will never overcome. While it is true that Java has had phenomenal growth, and significantly eroded the role of C++, it still has a long way to go. Java excels in portability and Internet support - but C++ still offers better performance and the ability to interact with the operating system.
Applets are inherently unreliable. The differences between Netscape and Internet Explorer make it impossible to write stable applets.
The problems with the behavior of applets running under browsers is due to the different JVMs - between browsers and browser versions. These differences can be frustrating for developers and users. There are often workarounds though, and applets should always be tested with a variety of browsers.