I’m doing a bit of consulting for a local health services organization. The environment is the predictable “LAMP” stack: Linux, Apache, MySQL and PHP. I’m about a half day into writing the PHP and remembering all of the reasons why I use ColdFusion: you have to roll your own solutions (or find somebody else who has) to elementary issues like escaping strings for SQL queries and other mundane programming issues instead of actually solving the business problem at hand.
More developers should get familiar with the CLAP stack: ColdFusion, Linux, Apache and PostgreSQL. For the same productivity enhancing reasons people are flocking to the fashionable Ruby on Rails, ColdFusion provides rapid application development and huge return on investment when combined with the other open source components without sacrificing stability or features. If you have the know-how, CF also exposes the full Java runtime engine meaning you can pull off about anything under the sun.
The two most frequent arguments against ColdFusion are that it’s not free (or open source) and that it is “slow”. Both of which are edge case arguments that ignore the 98% sweet spot ColdFusion serves so well.
Sure, ColdFusion isn’t free. It also might not handle Amazon.com-like traffic easily or cheaply. The good news is you don’t work at Amazon, a development license is free and ColdFusion hosting is widely available at competitive-to-PHP prices. Those arguments against ColdFusion are starting to sound a bit philisophical, no?
All Categories from Feedburner
Comments are closed.