As a ColdFusion developer looking for a job in the valley, I also faced all the negativity associated with the language. In fact, I ended up barely mentioning t

As a ColdFusion developer looking for a job in the valley, I also faced all the negativity associated with the language. In fact, I ended up barely mentioning the language on my resume. If the language was renamed to something else and totally re-branded, it would probably gain more respect. Most people still think of the older versions when it was built in C. But since the conversion to Java, it has been able to benefit from a lot of the Java enhancements while still functioning as a duck-typed language. Another advantage is that, it has a very short learning curve. But like with any tool, it can be used by amateurs to produce amateur looking code. Using a framework (eg. FW/1) encourages better structured code and OOP approaches. You can meet most of your web needs with ColdFusion and some highly specialized items may be more complicated. But that is the case with just about any language. The only part where I havent found sufficient documentation or user experiences related to scaling applications. That is not to say, it hasn't been done. Given the relatively high price of Adobe CF (compared to Ruby/PHP etc), it is not really an option that startups (in the Bay area) will consider. There are open-source CFML engines like Railo as the author notes, but unfortunately, it lacks publicity.