In the last years there were many reports in the media about Java security. All these security issues are related to vulnerabilities that allow the process to exit the sandbox boundaries.
These issues only affect the Java browser plug-in that executes Java applets in a sandboxed environment.
They have nothing to do with regular desktop or server programs. Those programs are not sandboxed and can access anything that the process owner can access, like any other program.
In fact due to the JVM memory model, Java programs are generally more secure than programs written in C/C++.
B4J doesn't create applets and doesn't rely on the Java browser plug in.
Note that Oracle plans to remove this feature in the future: https://blogs.oracle.com/java-platform-group/entry/moving_to_a_plugin_free
Informative discussion about this topic: http://security.stackexchange.com/q...-insecurities-are-other-languages-more-secure
These issues only affect the Java browser plug-in that executes Java applets in a sandboxed environment.
They have nothing to do with regular desktop or server programs. Those programs are not sandboxed and can access anything that the process owner can access, like any other program.
In fact due to the JVM memory model, Java programs are generally more secure than programs written in C/C++.
B4J doesn't create applets and doesn't rely on the Java browser plug in.
Note that Oracle plans to remove this feature in the future: https://blogs.oracle.com/java-platform-group/entry/moving_to_a_plugin_free
Informative discussion about this topic: http://security.stackexchange.com/q...-insecurities-are-other-languages-more-secure