Posts: 5,938
Name: Adam for web page design, not program
Location: Toronto, Ontario, Canada
|
I'm with chrishirst. I've done a bit of dabbling in PHP, but I cut my teeth back in 2000 on ASP and wouldn't use anything else.
It's not a matter of "better" or "worse"...it's a matter of "better for me" or "worse for me". ASP is better for me since AFAIK it's the only programming language which will allow me to build websites with an Access database. I can see people in the back rolling their eyes at that, but there is a business reason: most of my clients, if they have a database program at all, have and are familiar with Access. So they like the idea of FTPing to a server, downloading a database, making changes, putting it back up, and seeing them live. I've got about 5 or 6 clients like that.
That's not the only reason I use ASP, but it's one of them. Other reasons:
I find it easier to read.
I don't have to make that much of a mental adjustment when people ask me to code database stuff in VB (got a couple of clients that do that).
I can't stand using MySQL.
I've written over 2500 lines of custom functions and subs that will allow me to pretty much do anything I want in about 1/10 of the time that it would take most people.
I love when idiots who have no idea what they're talking about claim that ASP isn't scalable and reliable because they downloaded some unoptimized script, attempted to mod it without knowing what they were doing, found it crashed once or twice.
I love it even more when idiots who have no idea what they're talking about claim that ASP off of an Access database can't be used on a site that is even remotely successful. While it isn't exactly a top-end figure, I've seen sites that get as many as 60,000 page views per month run off of an Access DB and not even flinch at the resource usage. This isn't to say that Access doesn't have limitations, because it certainly does. But for 99.99% of sites, if coded properly, Access would be fine, just fine.
And if Access isn't fine, just fine, then there's always SQL Server, which is a pretty hardcore database to play with.
So there are my reasons. It really depends, though, on what you're doing.
|