> There is plenty of "sloppy code" in the .Net-i-verse...like you said, > it's ultimately about the developer, not the platform.
I'm not so sure about that. I've dabbled with .Net on and off over the last couple of years (every time I get depressed about job prospects in .CF ...) and each time I'm driven back to CF's big advantage (as I see it) over .Net - productivity. Microsoft seem to think that developers want to at the lowest level of nuts and bolts needed to put together their programs. By contrast, CF developers can keep their eye at the customers level while delivering applications in half the time taken for equivalent functionality in .Net I ponder the question as to why any Client and CIO would want to spend the extra money on writing an App in .Net (assuming they are aware of the productivity advantages of CF and other technologies); or indeed, on coverting an existing app written in CF to .Net (???) This seems wierd to me. The only answer that comes to mind is possibly that the CIO is interested in justifying his position, it is easy to represent CF as being older technology, and a move to .Net as being a move to newer more robust technology. With .Net he gets to be in charge of a much larger development team, and a bigger budget. Does that line of reasoning hold water ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330063 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
