|
I'll be glad for a fast-loading JRE. But fast isn't going to help me if the basics don't work. My problem is reliability. (And I am not alone--see http://www.dynamicobjects.com/d2r/archives/002859.html or http://www.salas.com/weblogs/archives/000529.html or http://www.javalobby.org/java/forums/t82957.html#92054708) I want to give the required JRE version in a descriptor (JNLP or whatever), and then I just want my app to run on my users' machines. I don't want to build an infrastructure of version-sensing JavaScript. I don't want my users to have to navigate a maze of incomprehensible gobbledygook. I don't want a significant fraction of my users tell me that the browser association was broken and all they saw is the JNLP file, or that the spinning coffee cup never stopped spinning, or that a splash screen briefly appears and then nothing happens, or their browser hung and they had to restart it. I don't want them to ask me what they should do with the 300 .jnlp files on their desktop. (I suggest they forward them to Bob Brewin :-)) |
java.net RSS Feeds
