While ASP & Java might get more press and dollars thrown at them. ColdFusion is really hurting these technologies, how so you might say. It hurts them in terms of productivity. Java, ASP & even PHP are just hard work, so hard in fact that you need to either spend a lot of time or employ a framework just to get you almost equivalent to ColdFusion.
It is evident to me that while Adobe need to better market ColdFusion than was done by Macromedia, Java and ASP people are quick to jump in with the it's crap, I thought it was dead type of comments. Funny that these people are even bothering to read such ColdFusion articles, what are they looking for if they have moved on. I know I'm not reading any Dig articles on ASP or Java releases.
They are also happy to jump in with the we moved here and did this and it's been good.
But here is my story, in 2001 I was a CTO in a division of a large public company. Decided to rewrite a 2.6 million ASP development in ColdFusion.
Straight away people were on my back, is that the right decision, ColdFusion is dying. ASP is much better, your making a mistake. Hang on, that's 6 years ago, surely the life support must have been turned off by now and they would have stopped releasing new versions.
More recently joined another public company as CTO and replaced a large and complex Java application again with ColdFusion.
Why would I do this, is it because I don't understand ASP or Java, not at all, have written lots of Java and ASP stuff, have recently studied at uni using PHP and Java, HD in every subject. The reason is that they are just hard work, sure Java might have a good new framework, but that's part of the problem. Had a team of Java developers that were always chasing a moving target and getting nothing done.
What do I mean my moving target, well they had a Java application that used various frameworks and libraries, but there was always a new one that they wanted to use or play with, we want to try hibernate, we want to use JSF.
All this costs development time and money. Even the developers couldn't agree on what frameworks to use.
So when I introduced ColdFusion, they all got scared, telling the business that I was crazy, I didn't know what I was doing and that I was making the wrong decision. But for some reason the business trusted me (The new guy) and not the rest of the team, perhaps I was very convincing when I pitched the idea of starting again to the board.
Now pitching to rewrite large applications, is not an easy pitch, it's not an easy or inexpensive process either. But to me it's simple, I've done this before, it works and the business will see the benefits.
So after spending the past 2 years rewriting all the applications (not
personally) in ColdFusion and building a 100% new development team, what is the result? A very good one, the functionality is superb, the development time is very low, there are less development staff required. And ultimately the business is happy.
We use 99.9% ColdFusion, there is one Encryption JAR that we wrote. But other than that it's all CF, pure OO CFC's with no framework, which I choose not to use due to the issues I've explained with Java framework moving targets.
In summary, I use ColdFusion because it works, it's easy and it's good for the business. I look forward to ColdFusion 8 and future versions, Adobe and the CF team have done a great job on this release and CF is now even further ahead of the competition.
It is evident to me that while Adobe need to better market ColdFusion than was done by Macromedia, Java and ASP people are quick to jump in with the it's crap, I thought it was dead type of comments. Funny that these people are even bothering to read such ColdFusion articles, what are they looking for if they have moved on. I know I'm not reading any Dig articles on ASP or Java releases.
They are also happy to jump in with the we moved here and did this and it's been good.
But here is my story, in 2001 I was a CTO in a division of a large public company. Decided to rewrite a 2.6 million ASP development in ColdFusion.
Straight away people were on my back, is that the right decision, ColdFusion is dying. ASP is much better, your making a mistake. Hang on, that's 6 years ago, surely the life support must have been turned off by now and they would have stopped releasing new versions.
More recently joined another public company as CTO and replaced a large and complex Java application again with ColdFusion.
Why would I do this, is it because I don't understand ASP or Java, not at all, have written lots of Java and ASP stuff, have recently studied at uni using PHP and Java, HD in every subject. The reason is that they are just hard work, sure Java might have a good new framework, but that's part of the problem. Had a team of Java developers that were always chasing a moving target and getting nothing done.
What do I mean my moving target, well they had a Java application that used various frameworks and libraries, but there was always a new one that they wanted to use or play with, we want to try hibernate, we want to use JSF.
All this costs development time and money. Even the developers couldn't agree on what frameworks to use.
So when I introduced ColdFusion, they all got scared, telling the business that I was crazy, I didn't know what I was doing and that I was making the wrong decision. But for some reason the business trusted me (The new guy) and not the rest of the team, perhaps I was very convincing when I pitched the idea of starting again to the board.
Now pitching to rewrite large applications, is not an easy pitch, it's not an easy or inexpensive process either. But to me it's simple, I've done this before, it works and the business will see the benefits.
So after spending the past 2 years rewriting all the applications (not
personally) in ColdFusion and building a 100% new development team, what is the result? A very good one, the functionality is superb, the development time is very low, there are less development staff required. And ultimately the business is happy.
We use 99.9% ColdFusion, there is one Encryption JAR that we wrote. But other than that it's all CF, pure OO CFC's with no framework, which I choose not to use due to the issues I've explained with Java framework moving targets.
In summary, I use ColdFusion because it works, it's easy and it's good for the business. I look forward to ColdFusion 8 and future versions, Adobe and the CF team have done a great job on this release and CF is now even further ahead of the competition.
