Hows that for an incendiary subject line? In my dabblings with ASP, I keep thinking how hard it is to work with , and that Cold Fusion can do the same task so much more easily and logically... There's a whole bunch of stuff that I take for granted with CF, and when I go to ASP, I really miss those features, for example:
The IsDefined() function. The ability to say <CFINCLUDE template="#aFilename#.cfm"> (i.e. dynamically supplying the name of an include file) <CFQUERY > vs 4 lines of DB connection crap Much more useful error messages. you get the idea... Then I start to think.. "Well maybe if I was a good ASP programmer then I wouldn't be relying on some of those CF-style programming constructs and would be just as efficient in ASP" So my question to the list is.. Is there anyone here who considers themselves a top-gun ASP programmer, or someone who started in ASP and has now moved to CF, and can say with some authority that Cold Fusion really is a more efficient language. A number that used to be bandied about was that a CF site would take approximately 65% of the development time/cost of an equivalent ASP site. Is that number anywhere near reality if you had 2 programmers equally adept in their development platform? As opposed to a lot of us who I'm sure have fiddled with ASP and gone "Bleahh that looks awful" (i.e. me). seeya! ----------------------- Ryan Sabir Newgency Pty Ltd 2a Broughton St Paddington 2021 Sydney, Australia Ph (02) 9331 2133 Fax (02) 9331 5199 Mobile: 0411 512 454 http://www.newgency.com/index.cfm?referer=rysig --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
