It looks like ColdFusion is in fact a dying language. (#5)

I’ve always knew that ColdFusion was a bit of a dinosaur, but this is more of a confirmation for me than anything else. ColdFusion is great for doing some things very well, that other languages don’t:

• One-Line commands that take at least 5 or 6 in other languages (like reading files)
• Getting smaller applications out the door very quickly

But as the article says… and I think this pretty much says it all:

Debates continue over whether ColdFusion is as robust and scalable as its competitors, but nevertheless, premiums paid for ColdFusion programmers have dropped way off, according to Foote. “It was really popular at one time, but the market is now crowded with other products,” he says.

Having recently attended cf.objective() which is not the premiere, but probably one of the largest ColdFusion conferences in the nation, I’ve seen this first hand. Object-Oriented concepts are just now being adopted by ColdFusion developers. Concepts like domain modeling were introduced, object-relational mapping are just now having frameworks developed.

For ColdFusion to really revitalize itself, it needs to do what ASP did when ASP.NET came out. A complete revamp. ASP.NET while nothing like ASP was a very welcome change because of the great new concepts that it introduced, like a windows-form like programming structure (basically Model-View-Controller), event-driven architecture and the .NET Framework. ASP.NET did some great things for Microsoft, and Adobe should take note of that.