I guess being an Adobe product doesn't really help. Adobe is associated with design, Coldfusion is a strange beast in Adobe's product range. It made some sense at Macromedia as they were more web- focused but even then it didn't feel right.
Adobe Coldfusion would be better of being a separate company or even better an open source product like most other serverside technologies. Which is why I see much more future for Railo or Open BlueDragon. We as a community should also do a better job at marketing these open source technologies which would help to change the perception about Coldfusion. We could e.g. start by adding a small "Powered by Coldfusion/Railo/Open BlueDragon" logo or text on all our sites. In any case just hire PHP, Ruby or ASP.NET, JAVA people whatever language background they have and if they don't mind switching they'll do just fine. I started with ASP switched to PHP, did Coldfusion, back to PHP and now back to Coldfusion it's all very similar. Going from Coldfusion to PHP is harder than the other way around. We have a saying about food (literarily translated into english): The farmer/peasant does not like what he does not know. If people don't know it they probably don't want it or have wrong a perception about it. -- tag/function ref: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
