That's not true. VBScript/JScript don't get run automatically in preview window. If the content is HTML, script tags are strip from it. In the case, it is a attachment, and has to be explicit run by user.
But I agree with your solution. They should not turn off all executable or script but have various levels of security to script Outlook. However, it is a fundamental design problem in Outlook and can't be patched over (not in 2 weeks anyway).
Java is (will be) successful in 2 areas. 1) Eventually replacing most script languages. JSP is really ASP using Java instead of JavaScript/VBScript. The convergence will come as more specialized packages come out for Java. 2) Eventually become the adcamemic language of choice. It is so easy to use it to teach OO. It will replace Pascal, Ada, Mod3,...
Java will remain a script-type language. Script languages can do a lot these days but it is hard to replace C/C++ for high performance applications. There are a few problems with its speed. Java is hard to optimize beyoud tuning algorithms. It is not as easy to know what exactly the JVM is doing (now with JIT and HotSpot) to the bytecode. It is still valuable to look at assembler at times to know how to tune C/C++ code. It is also hard to tune memory usage which turned out to be the bottle neck for many high performance apps. A good garbage collector is hard to write and even with one it still will never beat good alloc/free or even new/delete.
It is also simple minded to think that OS/Runtime and language can be totally decoupled and still perform well. OS designers have a set of languages in mind and language designers have some OS specific features in mind. To make Java as fast as C, you will need a Java-specific OS or Java chip.
Slashdot Mirror
That's not true. VBScript/JScript don't get run automatically in preview window. If the content is HTML, script tags are strip from it. In the case, it is a attachment, and has to be explicit run by user.
But I agree with your solution. They should not turn off all executable or script but have various levels of security to script Outlook. However, it is a fundamental design problem in Outlook and can't be patched over (not in 2 weeks anyway).
Java is (will be) successful in 2 areas. 1) Eventually replacing most script languages. JSP is really ASP using Java instead of JavaScript/VBScript. The convergence will come as more specialized packages come out for Java. 2) Eventually become the adcamemic language of choice. It is so easy to use it to teach OO. It will replace Pascal, Ada, Mod3, ...
Java will remain a script-type language. Script languages can do a lot these days but it is hard to replace C/C++ for high performance applications. There are a few problems with its speed. Java is hard to optimize beyoud tuning algorithms. It is not as easy to know what exactly the JVM is doing (now with JIT and HotSpot) to the bytecode. It is still valuable to look at assembler at times to know how to tune C/C++ code. It is also hard to tune memory usage which turned out to be the bottle neck for many high performance apps. A good garbage collector is hard to write and even with one it still will never beat good alloc/free or even new/delete.
It is also simple minded to think that OS/Runtime and language can be totally decoupled and still perform well. OS designers have a set of languages in mind and language designers have some OS specific features in mind. To make Java as fast as C, you will need a Java-specific OS or Java chip.