depends what it is you are trying to do and what the budget is.
if you have a small budget and coldfusion is available i would use coldfusion everyday and twice on sunday. this is because i find it quicker to develop in and has got more in built features (graphing engine, flash remoting, verity search, file upload etc).
if coldfusion is not available then asp is an alternative, it doesn't cost anything, if you are running IIS as its built in to the system, but if your not using IIS on windows then may i suggest PHP. started plaing with it and found it alot more friendly that ASP.
you can do most of the things that i mention above in ASP, but you would have to buy thirdparty add-ons to do these and some of them can be a real pain.
PHP does have some of the above functionality (if it has all i will be happily corrected still learning it you see!) and i found it alot easier to learn that the likes of ASP, but for me Coldfusion is still the winner.
you can download the developer edition from the macromedia website which is free, and it has all the functionality available to you.
the thing about asp "not costing anything" is that this is exactly what they want you to believe
asp runs on iis, right? and that runs on windows, right?
hey, no prob if it's a non-critical departmental intranet, maybe the cafeteria menu, if it goes down, you just reboot the server
but you're not going to expose windows/iis to the outside world on the internet, not without an army of very highly trained, highly paid network engineers, security experts, and certified data base administrators
As a CF veteran (tagging since 3.0), I have to put in my EUR.02 here.
ASP, as everyone knows and loathes it, is history.
Sure there are maintenance jobs to do, but that's irrelevant.
The real discussion should be about CF versus ASP.NET. One class ought to be enough to convince you that the .NET monster is the wave of the future. Robust? Holy moley, is it robust. Scalable? Off the scale. Flexible? Rapid, built in conversion to a Web Service, to a Windows app, to what you need. True XML manipulation, not this bass-ackwards WDDX stuff.
What I never understood about CFMX is why the heck they decided 1) to introduce another layer in the data connectivity area (Java? we don't need no stinking Java!); 2) to trash, no, mutilate, a perfectly good development environment; 3) to drop DSN-less connections after v5 (duh!); and 4) to bury the command-line utility.
Take a stroll through the MacroMedia CF forum, and gawk at the ton of problems associated with this J2EE nonsense. It's enough to make us come to a screeching halt in our upgrade path, right before the cliff that is CFMX. My little ol' 4.5.2 apps are humming along just fine, thank you.
Maybe, just maybe, they'll turn it around with the next upgrade, but I'm not holding my breath. I have to design my next ASP.NET app.
(And it's a shame that it had to come to this....)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.