13 reasons why Ruby, Python and the gang will push Java to die… of old age | Little Tutorials

25 Dec 10

Dawiiid unknown

performance scripting languages

29 Dec 09

Giovanni Lofrumento

linguaggiProgrammazione

15 Dec 08

Todd Medlin

languages

08 Nov 08

Kent Yu

language ruby Delicious

25 Jun 08

Richard Tibbetts

programming languages trends delicious

08 Jun 08

Rich Hintz

Java is gonna die eventually of old age many many years from now.
I will share the reasoning behind my statement. Let’s first look at some metrics.

ruby java development comparisons software

03 Jun 08

vikramsjn

Lately I seem to find everywhere lots of articles about the imminent dismissal of Java and its replacement with the scripting language of the day or sometimes with other compiled languages. No, that is not gonna happen. Java is gonna die eventually of old

programming language comparison java python ruby deliciousExport20110319

02 Jun 08

David Lounsbury

programming software languages java ruby

01 Jun 08

ifwe ddf

Ajax C# java Jobs to python ruby programming comparison

Seçkin Anıl Ünlü

No, that is not gonna happen. Java is gonna die eventually of old age many many years from now.
What I find significant here is the huge share the “C like syntax” languages have.
Reason number 1: Syntax is very important because it builds on previous knowledge.
Reason number 2: Too much noise is distracting. Programmers are busy and learning 10 languages to the level where they can evaluate them
nothing really is earth shattering. There are seasonal variations but in long term nothing seems to change.
Reason number 3: Lack of pressure on the programmers to switch. The market is pretty stable, the existing languages work pretty well and the management doesn’t push programmers to learn new languages.
Reason number 4: Challenger languages don’t seem to catch momentum in order to create an avalanche of new projects started with them.
Reason number 5: Challenger languages communities don’t do a good job at attracting programmers from established languages.
Reason number 6: There is no great incentive to switch to one of the challenger languages since gaining this skill is not likely to translate into income in the near future.
To do this it has to leverage things those programmers already know. (C++ built on C, Java built on C++, C# built on C++, Java and Delphi)
Java managed to cover two problems plaguing the C/C++ world: complexity (C++) and memory management (C/C++)
Reason number 7: The new languages don’t introduce an earth shattering improvement in the life of most of the programmers and projects.

Reason number 8: There is no killer application on the horizon.
Reason number 9: None of these new languages has a powerful sponsor with the will and the money to push them on the market.
Reason number 10: Most of these languages lingered around too much without stepping decisively into the big arena.
Reason number 11: “Features” that look and are dangerous for big projects.
Reason number 12: Unnatural concepts (for majority of programmers) raise the entry level.
Reason number 13: Lack of advanced tools for development
Scripting languages (Groovy, Rhino…) on top of Java and the JVM are interesting but they will never be primadonnas. They cannot compete with Java because they are slower.