ColdFusion never made it… then it “died”

Lists seem to draw the most attention. Much more attention than things like research and journalism. These reporters can get away from their criticism for the well known reason that any press is good press. I don’t think Corfield’s ever common quote “If you’re not annoying somebody, you’re not really alive.” is true in this case. The post I’m referring to of course is the recently Dugg Ghosts in the Machine: 12 Coding Languages That Never Took Off (link to Digg, they’re not getting the hits) which lists 12 languages they claim have, obviously, never made it big. The ColdFusion community struck back in force on the Digg post which had me wondering. Are they wrong? Did it “take off” compared to other technologies in the market? Well, Indeed.com to the rescue!

ColdFusion or Cold Fusion

Odd, it seems as though 3 of the 12 languages have a decent amount of jobs currently. The other 9 are admittedly on the low side with .001> of all jobs using these. What’s funny to me is that not only is ColdFusion the most popular on the list, but ColdFusion spelled wrong is more popular than the others. The number of ColdFusion, Delphi and Powerbuilder jobs have slightly declined in the past two years, which in all cases could be only the beginning of an eventual fall from “grace”, but these are still interesting numbers. Where do these three compare with other scripting languages?

ColdFusion vs Scripting languages

Here’s some other contenders, albeit in a slightly different realm. Python, Ruby and Ruby on Rails are outshine ColdFusion on the Tiobe index, but when you combine the two spellings of ColdFusion it has the largest number of jobs of the bunch (or very close). What does this mean? It means the article is wrong, and not well researched; unless they make the claim the others never took off that is — especially since Ruby came out the same time as ColdFusion, and Python even before that. This doesn’t deny the fact though that Ruby and Python are growing rapidly while CF is not. While we can blame poor marketing by Adobe, the high price or sensational reporting like this for the lack of growth, the real reason could just be that the others are a better fit for more places. With more smaller companies getting into the web now than ever before, and initial startup cost being such a prohibitive part, things outside a LAMP stack are a luxury better spent elsewhere. But that’s the obvious reason - what if more people coming out of college with java backgrounds just click more with tagless languages? These reasons are enough to get many people to steer away I’d think. I might be getting a little off track. Whatever language you choose, good for you; they all do the same thing. Just get something done and call it a day. :)

If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments
I really think you should review your judgment…CF is far from being dead, it is used in so many institutions,companies…and because of the boost of Flex, CF will be even more used as the integration with Flex is really wonderful so…yeah, keep saying that CF is dead…it means more jobs for us :))))
Ah, I was being sarcastic about the dead part actually. Recently there was another sensationalist article about “dead languages” and with this article about “languages that never made it” it seemed funny to me that they contradict each other. I’d say ColdFusion is as alive as ever though, with a more active community than ever before.
@Francesco - I really think you should read posts before passing judgment on them :))))
ColdFusion is platform that is squarely targetted at developing web applications.

How about a comparison against platforms that also do that. For example J2EE, or .NET.

There’s a reason I didn’t do that actually. This wasn’t a general comparison of the features of ColdFusion compared to those of Python or Ruby, it was comparison of where they stand in the marketplace to disprove the article that ColdFusion had “never made it”. It wasn’t an attempt to prove the article wrong, not to give an overall comparison of why you should or shouldn’t use ColdFusion. To do this comparison with .net and j2ee doesn’t work though see here for why, so I found some technologies in the same market share as ColdFusion to base my case. I could’ve used PHP, as PHP and ColdFusion are surprisingly close and both built completely for web aps (although, of course, ColdFusion offers more deployment options and backend language tie-ins). But a comparison against j2ee and .net for market share doesn’t show CF favorably so it was left out.
Good find Adam! I love seeing people take the time to prove why Coldfusion isn’t dead… I hate the criticism it receives so much.

Whatever it may be…

Let them think its not worth it, like Fransisco said, “yeah, keep saying that CF is dead…it means more jobs for us ”

Coldfusion for the win!

Hmm, what’s the problem here? Is your math wrong?

“…When you combine the two spellings of ColdFusion it has the largest number of jobs of the bunch (or very close). What does this mean? It means the article is wrong…”

Perform the individual searches as of today, and this is what you may see:

cold fusion: 2106
coldfusion: 2584
delphi: 1763
rails: 5949
ruby: 3044
ruby on rails: 1089
php: 9813
powerbuilder: 1746
python: 5566

cold fusion + coldfusion: 4690

Which doesn’t put it at the top of those you listed. It would be in third place behind “rails” and “python.” (”php” was not in your original analysis.)

@Forest
I did only mean of those on that one chart which has python and rails as the top competitors, so PHP is out. The term “rails” though should be a subset of “ruby” and “ruby on rails”. That would be like searching for “cold” in my opinion. Rails will list jobs that aren’t ruby more than any other searches.

If Python is at 5566 though, it does top ColdFusion as of now.

Leave a comment

(required)

(required)