> Ah yes, the old "use Java when CF can't do it crutch." > > I though the whole point of CF was to make it easy for developers to > develop. And everything else is hard/takes longer/is more expensive. > So why do I want to use something hard like Java to do something in > CF?
The "whole point of CF" hasn't changed since the Allaire's started the company: 1) To abstract the complexity of common web application tasks making it easy to quickly develop reliable applications. 2) To provide standard's-based support to allow those not-so-common tasks to be completed as well. This has been the basis since version 1.x. Look at the versions: everything ever added to the language was added to address common complex tasks. Those tasks that are not so common were made possible through the extensive standards support (COM, CORBA, JAVA, CFXs, JSP, etc). ColdFusion never, ever, not-even-once-when-it-was-drunk, purported to "do everything". It will do well over 90% of what well over 90% of web application developer's need out of the box. It won't create desktop applications (like Java or .NET), it won't create OSs or drivers or anything else - just web applications. When complex thread handling becomes a common need for web applications (and it simply isn't) then ColdFusion will make it easier through absctraction. Until then Coldfusion will make it possible via it's incredible extensibility - and the CF community will make it easy. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - CFDynamics http://www.cfdynamics.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:187453 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
