| |||||||||||||
Java and Memory ProtectionsJava and Memory ProtectionsPosted Nov 22, 2006 18:20 UTC (Wed) by jwb (guest, #15467)In reply to: Java and Memory Protections by tzafrir Parent article: Virtual Machines and Memory Protections
To me, the meat of the problem is that "safe" code (C#, Java) is allowed to call native libraries. It then becomes possible for the "safe" code to exploit flaws in those native libraries, which is obviously unsafe.
The nice thing about Java is you can easily forbid calling native code.
(Log in to post comments)
Java and Memory Protections Posted Nov 22, 2006 19:16 UTC (Wed) by bluefoxicy (guest, #25366) [Link] > The nice thing about Java is you can easily forbid calling native code.
C# can do this as well. The thing is, sometimes you actually need the functionality present in the native libraries. F-Spot uses libpng to show PNG images, and libjpeg to show JPEGs. As well, Mono uses Gecko and .NET uses IE to supply the Internet Explorer Web control from .NET, which has obvious implications; if you want to write a Web browser, are you going to be forced to write it all in C#, including render engine?
Java and Memory Protections Posted Nov 22, 2006 19:22 UTC (Wed) by jwb (guest, #15467) [Link] I don't see why not. Java provides pure Java (not native) PNG and JPEG routines, as well as pure Java cryptography, pure Java compression, and the rest. Oh, and there are also pure Java web browsers.
Java and Memory Protections Posted Nov 22, 2006 19:25 UTC (Wed) by bluefoxicy (guest, #25366) [Link] Sun Java does. What about GNU Classpath? Kaffe? Project Harmony? IKVM?
Java and Memory Protections Posted Dec 3, 2006 12:57 UTC (Sun) by fjalvingh (guest, #4803) [Link] One good reason to go native is performance.. Although Java performance is usually great you can get huge performance gains using assembly for specialized problems (like image encoding/decoding/filtering for instance)
|
|||||||||||||