Who considers ColdFusion a legacy language?
Posted by Steve BrownleeJul 10
How uninformed do you have to be to consider ColdFusion a legacy language? I noticed a trackback to one of my posts about using overloaded Java methods when calling them via ColdFusion. I visited it just see what they had to say, and although it just turned out to be a aggregator post, I noticed the following sentiment.
“…Steve Brownlee explores how to use overloaded Java methods in what is considered by many a legacy language…”
What “many” is this, or is it just the author extending his own beliefs on to an unsuspecting larger group? I seriously can’t believe that any group of people who have the faintest level of skill, talent or interest in web application development consider CF to be legacy.
You must be new here.
Google “Coldfusion is dead” and be amazed.
Even better: “but nevertheless still has a great installed base from the early web years”. yep, still using CF3 all right. Absolutely no new versions whatsoever. Who needs ‘em
Adrian, no I’m not new, and I know all about the Computer World article and the occasional buffoon who spouts off on ColdFusion. However, it still burns me to see this kind of ignorance.
Are we going through this again? Of all the things that need to be dead, that old saw needs to be killed. have a stake driven through its heart, head chopped off and buried at a crossroads. In other words its got more lives than the star of a cheap vampire movie.
In this area (northern Virginia/Washington DC/maryland) CF i s more than alive and well.
It is not legacy but it really needs more, more, MORE work. Two hints. Try these:
and then just call it:
or this:
Why CF compiler is so blind? Why you have to figure out where the problem is? It is compiler which should tell you where these mistakes are. Just imagine that in sample 2 you have dozens of nested arrays and structs. How do you think - how long it would take you to find there is comma missing?
There are people who say CF is mature language. I don’t agree. There are so simple mistakes in the code.
I understand CF is getting better and new functions are added but really - Adobe has to take step back and really test what they already have.
Code 1:
<cfcomponent>
<cfproperty name=”test” type=”string” />
<cfscript>
</cfscript>
<cfproperty name=”otherProp” type=”numeric” />
</cfcomponent>
and call:
<cfset o = createObject(”component”, “test1″) />
Code 2:
<cfset arr = [ { someKey="no comma" otherKey="where is the error" } ] />
@Radekg - sure, there are some flaws and eccentricities in CF, not only the ones you point out but others too.
I’ll still take CF with those flaws, hands down, over any other web dev platform.
If I remember correctly ASP, PHP and CF are all about the same age. CF versions are still actively released and the developer community sure does not seem to be getting smaller. Sure I see CF people doing more like Flex and Java. I just wrote a CF site that used some low level java socket stuff to connect to a 20 year old application, now that is legacy.
Hard to consider a technology “legacy” when it’s been given the 2008 Codie award for best web service solution.
http://www.talkingtree.com/blog/index.cfm/2008/5/21/SIIA-2008-Codie-Award-For-Adobe-ColdFusion