On Mar 25, 1:54 pm, Joshua Marinacci <[email protected]> wrote: > That's why caching is > important and why JavaFX hitting 100m downloads of the runtime is > important. It means that there are 100m desktops that can run your > JavaFX app without having to download the runtime. (100m was in feb, > i'm sure it's 200m+ by now).
Downloads don't matter because of the "multiple download problem", runtime penetration does. I believe that since JDK 6u11, JavaFX is included in the JDK, so I already racked up two JavaFX downloads because I got u11 and u12, and I will get one more with each new JDK release. The same is true for JRE downloads, if the JRE includes JavaFX. So the JavaFX team should publish the penetration rates, similar to Flash (http://www.adobe.com/products/player_census/flashplayer/ version_penetration.html), as a better way to measure how widely distributed JavaFX is. Also after a while, you will have exhausted all the computers that JavaFX can get to easily (early adopters, JDK 1.6 auto-update), and then it becomes a lot harder to gain more market share. Look at Microsoft: They push Silverlight through their web page, through Windows Update and through attractive content, and they don't even publish their penetration rate, probably because it's too low (said to be about 25% worldwide). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. 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 -~----------~----~----~----~------~----~------~--~---
