To me, that whole story sounds like an expensive failure.
Of course, the fact that it was a ColdFusion to Java transition has drawn a lot of comments from the CF community but most of those comments focus on the CF side of things and the suspicion that MFG.com didn't do its research (I personally suspect they got hooked in by an "enterprise" consulting group who started them down the Java tracks).
Whilst we can all sing the praises of CFML and criticize MFG.com for many things, I think we all need to look at the business aspects of a three year project to relaunch a web site in this fast-paced world. Yes, I'm sure it was a massive project and involved a lot of integration work but even so, macromedia.com was completely rebuilt from the ground up in less than that - and Macromedia's complete ERP replacement project (with 38 integration points!) was also completed in substantially less than three years...
My assumptions: - I am focusing on very dynamic, constantly changing websites that are there for the long haul, and development teams greater than 2 resources that will have rotating over time - the site will need a framework, coding standards, releases processes, and scheduled refactoring i.e. real, maintainable websites (the goal of any website regardless of its start). - The level of experience of the CF developers and, say, the Java developers are at an intermediate to senior level. They know their stuff and have a good solid background in the type of website above i.e. real, experienced programmers who are concerned about processes and standards that will see the site through a number of years (the goal of any developer regardless of their language). Thank you, David Tannersyn
There are still substantial productivity benefits in ColdFusion over Java or .net. If you were really concerned about ColdFusion, you would do better to look at Groovy or Ruby.
Ruby is still an outsiders choice in large corporations and there is still an overhead in keeping up with the quickly evolving deployment infrastructure.
Groovy is excellent. The productivity of a dynamically typed scripting language but deployment through standard WAR files. It's also really easy to integrate Java and Groovy if you need better performance in certain aspects of the application.
With ColdFusion (especially Railo - an open source CF engine which to me competes squarely with Groovy) you also get the productivity benefits and it's a much more mature infrastructure. Today there are probably more CF devs than groovy devs and you don't have to work around the bugs that still slow down Grails development.
You could also look at Python, but I think despite Googles support that will lose ground, or newer languages like Scala or Clojure, but they're a little esoteric for regular business web apps unless you need to handle concurrency issues or love lisp style meta-programming.
1.) Its not Legacy technology. Non developers need to know that it isn't a Legacy
2.) Let's talk about the aspects of the CF that are better. C# have struggle with things that CF can do without any effort.
3.) Some one many years ago showed me CF. I need to show it for others. That way they know there is more out there than ASP.Net and Java
~~~~~~~~~~~~~~~~~~~ Slightly off topic. The .Net developers I work with are blown away by <cfdump>, <cfwddx> and query of queries.
There is no conceivable way you can tell me that the business assumptions, and technology options available on day 1 were the same as on day 1095. IT has been on a massive growth phase over that time.
The reason why the CF community is passionate about CF is because the deep tool set and rapid development options allow us to reduce the lead times between business problem and business solution.
There are NO technology problems, there are ONLY business problems. ColdFusion allows us to concentrate on the former, and not worry about the latter.
