Why does Java insist on this dated system-wide VM paradigm? Just make the JRE an embeddable library. Apps like IntelliJ and Java games like Wakfu use their own internal JRE and don't rely on a system level JRE. Games like Wakfu auto-update when you run them, and don't expose the user to any more security risk than a C++ game and don't bother the user with extra JRE update notifications.
The big security issue with Java is the web applet system. If a user downloads a malicious app and runs it, it is the fault of the user, not the fault of C++ or whatever language or development tool was used to write the malicious app. However, when someone opens a webpage with an embedded malicious Java applet, and the applet sandbox fails to stop the applet from causing harm, that's Java's fault, not the user's fault. Shouldn't dev tools make it as easy as possible on the user? Users's shouldn't have to understand or care about which development items were used to create an application. Moving to a JRE as an embeddable library solves the security issue, solves the update nagging issues that users complain about, and solves user compliance issues of not choosing to install Java or not having a recent version of the JRE. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/WbILP0GpyNAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
