JDK version popularity
in [Java Programming]
|
From: Lew on 22 Mar 2010 19:28 Andrew Thompson wrote: >> Oh, so you are not bothered with knowing the stats. for amateur dev. >> firms? Tom Anderson wrote: > No, because they're a contradiction in terms - a firm is a business, and > a business is not amateurs. They might well be incompetent, but by > definition, not amateurs! By one definition. There is a definition in common use that allows a professional (i.e., someone paid for their work) to be an amateur: <http://en.wiktionary.org/wiki/amateur> "3. Someone who is unqualified or insufficiently skillful." Pretending that definition does not exist or is not a very common use of the word is disingenuous at best. -- Lew
From: Arne Vajhøj on 22 Mar 2010 19:45 On 22-03-2010 13:09, Lew wrote: > On Mar 22, 12:15 pm, Nathan<nathan.f...(a)gmail.com> wrote: >> Sigh... forgive my imperfect wording. I did mean the JRE being >> targeted, not the JDK - apologies. >> >> For a Java component developer it is useful information to know which >> JRE version is commonly targeted. I am aware that a lot of developers >> are working with 1.5 now. I am mostly curious about how many have >> switched to 1.6 already. > > This depends heavily on the target platform. The statistics for the > Java plugin are available at > <http://www.statowl.com/java.php> > which I found via > <http://www.google.com/search?hl=en&q=Java+version+statistics> > > These guys assert that in February, 2010, roughly 64% of browsers have > Java 6, roughly 12.5% have Java 5, nearly 20% were unknown, and the > other nearly 4% had Java 1.4 or earlier. This is consistent with the > fact that Java 5 is about five-and-a-half years old and all version > from Java 5 on back have passed their End-of-Service-Life periods, and > the fact that for browsers it's both relatively easy to stay current > with Java and relatively common for people to stay current with their > browser versions. Note that traditional Java applets is a bit obsolete today. JavaFX is the solution in this market to battle Flash/Flex og SL. > The application market will be significantly different, as will the > server market. Unfortunately, my google-fu was not strong enough to > find those numbers on your behalf within the time I was willing to > devote to your question. Perhaps your search will yield better > results. I don't know any either. Arne
From: Andrew Thompson on 22 Mar 2010 19:49 On Mar 23, 1:45 am, Tom Anderson <t...(a)urchin.earth.li> wrote: > On Mon, 22 Mar 2010, Andrew Thompson wrote: > > On Mar 22, 5:43 pm, Nathan <nathan.f...(a)gmail.com> wrote: > >> Where can I find statistics.. > > > Ahh. Lies, damned lies, and statistics! > > >> ..on JDK version usage in the Java > >> development industry?.. > > > Of what use the the statistics on *JDK* usage by *developers* of any > > relevance to anybody? > > > I can understand wanting to know what target *JRE* they aim their app. > > at, but that in no way depends on the JDK version they use to compile > > code. > > That is technically true, but pedantic and unhelpful. .. I think RGB covered an actual situation where it might be relevant. > ..If you're targeting > 1.5, you will generally be developing with 1.5. No reason to use anything > earlier, and no advantage, only risk and annoyance, to using anything > later. Obviously you are a neophyte at cross-compilation. In the last year, I have developed applets compatible with 1.1, APIs aimed at 1.4, and end user apps. that require either 1.5 or 1.6. Using -bootclasspath option and the appropriate rt.jars, this is trivially easy. I neither know nor care whether I can get JDKs for Ubuntu Linux that cover those versions, since I collected the rt.jars while I was using Windows. But I do remember that you were in for a 'world of pain' if you tried installing a pre 1.5 JRE/SDK on Windows after installing something 1.5+. -- Andrew T. pscode.org
From: Arne Vajhøj on 22 Mar 2010 20:02 On 22-03-2010 19:49, Andrew Thompson wrote: > On Mar 23, 1:45 am, Tom Anderson<t...(a)urchin.earth.li> wrote: >> ..If you're targeting >> 1.5, you will generally be developing with 1.5. No reason to use anything >> earlier, and no advantage, only risk and annoyance, to using anything >> later. > > Obviously you are a neophyte at cross-compilation. > In the last year, I have developed applets compatible > with 1.1, APIs aimed at 1.4, and end user apps. that > require either 1.5 or 1.6. I would do that for just for fun code. If it were serious code, then I would get the real thing. > Using -bootclasspath option and the appropriate rt.jars, > this is trivially easy. I neither know nor care whether > I can get JDKs for Ubuntu Linux that cover those > versions, since I collected the rt.jars while I was > using Windows. But I do remember that you were in for > a 'world of pain' if you tried installing a pre 1.5 > JRE/SDK on Windows after installing something 1.5+. It have done it many times without problems. All the regular stuff works fine. The last installed Java has a tendency to make itself the default Java in the browser, but that can be changed back. Arne
From: Nathan on 23 Mar 2010 00:09
> Desktop apps: most, my guess: 75-90% > > Server apps (Java EE): less, my guess: 20-33% Those are the numbers I'm after - I would have guessed approximately the same, but it helps to hear someone agree. Anyone else agree or disagree with this estimates? |