http://www.tekool.net/blog/2009/01/23/java-jre-version-penetration-stats-with-google-analytics/
1.4.2+: 700 (69.86%)
1.5+: 661 (65.97%)
1.6+: 568 (56.67%)
this would mean that 30% user use under 1.4.2 ?!
it seems when statistic come from non java website
http://forums.java.net/jive/thread.jspa?messageID=317425
EDIT : the 14th post say 67% under 1.4.2 , that’s a lot
[quote]1.6.0_00 to 1.6.0_09: 530 (52.89%)
none: 300 (29.94%)
1.5.0: 93 (9.28%)
1.6.0_10: 38 (3.79%)
1.4.2: 39 (3.89%)
1.8.0: 2 (0.2%)
[/quote]
Java 1.8 :persecutioncomplex:
What happened to 1.7 heh…
I was also wondering about Java 1.8. It either a bug in the deployment toolkit or something mac specific. I got 86 visitors with java 1.8 in the last 30 days - all mac users.
That ‘30% have no java’ seems a bit high to me - eg for 5359 visits I got 4683 have java (of some sort!) 676 don’t have java. That’s 14% - still way too high though!
Well this is only one source with a sample size of 1002.
A actuate conclusion would need to be taken by multiple sites and larger sample size.
Maybe Apple felt so bad about having us permanently behind with 1.6 that they made a time machine, went into the future, and then ported 1.8.
[quote]That ‘30% have no java’ seems a bit high to me - eg for 5359 visits I got 4683 have java (of some sort!) 676 don’t have java. That’s 14% - still way too high though!
[/quote]
no, this does not mean they have not java, that means they have a java version under 1.4.2, also getting statistic from non-Java related website give better result, for example I got only 7% but my own website is very java specific wich make statistic false.
More stats:
http://riastats.com/
It also uses Sun’s Java detection script. The fact that 1.8 is showing up makes means the detection script is not accurate.
i already sent them a mail yesterday 
thanks, great information, that confirm that around 25% user have still a java under 1.4 or no java.
I wouldn’t take that site’s data at literal truth - The detection script obviously has problems. Plus, it includes mobile browsers, game console browsers, etc.
ok, but other non-java statistic as the first I have posted show approximatvly the same result, this may be not exact but I think that it is near to the reality.
Well, they show the same result because they use the same java detection script. Although yes they’re probably not far from reality.
For desktop-only, Adobe shows 19% desktops don’t have Java, which is probably the most accurate:
http://www.adobe.com/products/player_census/flashplayer/
Although, the people who play web games is probably closer to 5-10% w/o Java.
I have done some test with deployJava.js on Window XP SP3
IE6 => detected
FF2 => detected
Safari => not detected
I also have MS JVM 1.1 on IE6 and even with sun plugin disable it was not detected, like no-java even if browser run Applets fine and even if there is something in the script to detect MS JVM.
FF2 on MacOS:
Java Deployment toolkit: 1.5.0
JavaFX deployment toolkit: 1.5.0_16
mime types: Java: undefined
Safari on MacOS
Java Deployment toolkit: 1.8.0 (wooow!)
JavaFX deployment toolkit: 1.5.0_16
mimetypes: Java: 1.5.0_16
=> JavaFX rulez!
IE8 on Windows - with MSVM installed:
Java Deployment toolkit: 1.5.0_17, 1.6.0_02, 1.6.0_14
JavaFX deployment toolkit: 0 - unknown
mime types: Java: undefined
So none of them got it right - depressing.
If it wasn’t because of the fact that we get a f* icon and a baloon every time the launch the VM (who on earth ever decided that, moronic) - it’d be best to launch an VM using the applet tag and just query the VM.
Ubuntu FF3 6u14b02
deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: 1.6.0
JavaFX deployment toolkit: 1.6.0_14-ea
mime types: Java: 1.6.0_10
Windows XP FF3:
deployment plugin available -> plugin2 detected
Java Deployment toolkit: Java: 1.6.0_14
JavaFX deployment toolkit: 1.6.0_14-ea
mime types: Java: 1.6.0_14
Windows XP IE6:
deployment plugin available -> plugin2 detected
Java Deployment toolkit: Java: 1.6.0_14
JavaFX deployment toolkit: 1.6.0
mime types:
Windows XP Google Chrome:
deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: 1.6.0
JavaFX deployment toolkit: 1.6.0_14
mime types: 1.6.0_14
[quote]If it wasn’t because of the fact that we get a f* icon and a baloon every time the launch the VM (who on earth ever decided that, moronic) - it’d be best to launch an VM using the applet tag and just query the VM.
[/quote]
this is what the jfx dt actually should do as fallback mode. it even uses cookies to do it only once. I helped to fix a bug in the jfx dt but i don’t know if they are already integrated in the public script.
Matzon and everyone with a not working javafx dt, could you check out this page (it uses a different version of the script):
http://jim.campanell.com/sun/JavaVersionDetector.html
@java script experts, is it possible to use two versions of the same script on the same page without conflicts?
installed now opera and safari on my xp box too
WinXP Opera 9.64 6u14b02
deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: none
JavaFX deployment toolkit: 1.6.0_14-ea
mime types:
Safari 4 Beta (528)
deployment plugin not available -> plugin2 not detected
Java Deployment toolkit: Java: none
JavaFX deployment toolkit: 0 - unknown
mime types: Java: undefined
(Safari -> FAIL, but applets work…)
[quote]Navigator contents:
appCodeName = “Mozilla”
appName = “Microsoft Internet Explorer”
appMinorVersion = “0”
cpuClass = “x86”
platform = “Win32”
plugins = “”
opsProfile = “null”
userProfile = “null”
systemLanguage = “en-us”
userLanguage = “da”
appVersion = “4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)”
userAgent = “Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)”
onLine = “true”
cookieEnabled = “true”
mimeTypes = “”
Browser is MSIE
Java Version is 1.6.0
OS is Windows
Mac OS Version is Not Mac
Can we handle version info? Yes
[/quote]
This is not correct, in that it IS Internet Explorer - but the applet tag is handled with: Microsoft ® VM for Java, 5.0 Release 5.0.0.3810.
not directly, you will get method and var collisions - you will have to rename all the methods and vars.