One of the biggest arguements I have seen is the cost issue. Most of the time it starts with "well CF is more expensive to start with, but you save in development time so the cost really isnt a concern". Im sorry but that is a load. Sure, you take a CF expert who also happens to know a little ASP and yes they are going to develop their app faster in CF. But if you take someone who has been using ASP for years and knows all there is to know, there really isn't a significant difference in development time. I have been on both sides and both technologies are good. Each is just good for different things. As for cost though, I still havent seen any real evidence of CF being cheaper than ASP. For the record, I would still choose CF over ASP on most apps, but I still think ASP is awesome.
Misty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 07, 2002 10:41 AM To: [EMAIL PROTECTED] Subject: RE: [KCFusion] ASP vs CF Robin, you're right, but your remarks are based on logic. My reason for gathering ASP vs CF information is to deal with the mentality that says "Microsoft has most of the desktop OS market, so all their software must be the best in the world". It's amazing how many people think like this. Like you, I prefer an informed decision. Which is why I'm trying to gather rational information to counter irrational assumptions. Not disagreeing with you :-) Keith Purtell, Web/Network Administrator VantageMed Operations (Kansas City) Email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Greenhagen, Robin Sent: Tuesday, May 07, 2002 10:20 AM To: [EMAIL PROTECTED] Subject: [KCFusion] ASP vs CF In advance, sorry about the long drivel below :-)... I think that it is important to realize that the ASP vs. CF argument is a bit misleading when trying to build up the feature by feature comparison. We have been CF centric for 5+ years, but still write ASP apps for people if their environment, their staff, and their needs dictate it. Once you have technique in either tool set, there is less of difference in productivity than either group claims. I think comparing on a feature by feature basis is like looking at WordPad (ASP) vs. MS Word (CF). When was the last time you used CFAUTHENTICATE or CFLDAP? But your server loads that code up every time you start the CF services. One advantage to the ASP model of components (3rd party controls to do mail, encryption, credit cards, etc...) is that if we don't like one, we can pitch it and use one of the other 10 vendors out there. We have had to do this in the past when a CF component (CFPOP or CFHTTP) failed to meet our needs. So either way we incur the expense of buying the control that we like, but with CF, now I have two solutions loaded on the box, and I have to use CFOBJECT, which has had it's own issues. In the past we have felt like Alliare was the 3rd camp (ASP and J2EE were the two most visible, widely used tools). Now CF truly has an alliance with the Java camp in CFMX, and great interoperability with the .NET (formerly ASP, COM, ActiveX) camp. But if a company is deploying desktop applications in VB.NET, it will be a hard argument that they shouldn't deploy the web interfaces for that app in ASP.NET. There is no definitive right/wrong decision matrix that can account for all project variations, etc... What I believe was the biggest single accomplishment in CFMX won't be mentioned by Macromedia. They have essentially ensured that CFML will live for the next 10 years by implementing it on the J2EE platform. As a standalone, single vendor, propriety language, app server solution, someone could have easily said "we are shelving CF and pursuing JSP/J2EE" as about 10 - 20 other app server vendors have done. Now even large organizations that have $xxx,xxx,xxx worth of BEA Weblogic and IBM Webshpere can use CFML to get the job done. These development groups that have been implementing CF as an "unsupported" application on their networks can now take the approach that this is the CFMX tool for Weblogic/Websphere and run it in a fully supported production environment. Cheers! Robin Greenhagen President GSI http://www.gsi-kc.com/
winmail.dat
Description: application/ms-tnef
