ASP versus PHP

Not open for further replies.
David (Behan) do you use VBscript with ASP pages?

I've been going over VBscript and I can't fathom why the language was designed as it was.
Why does it have to be so verbose? "dim","sub","end if". I don't know why they had to rewrite the book on how to declare functions, and why not use good old braces?

Also, the worst thing I believe is that they use single quotes ' for comments! How ridiculous!
asp is different from php by those things mentioned by you above.
they do make sense outlined below
dim in asp is setting a variable in php $str=NULL; or a value otherwise you get a php error

sub is similar with functions
end if is equal to closing } bracket.
It makes sense.
Now in asp you don't have to close every line with ; where in php you get an error if you don't.

I thing those things makes the 2 languages different.
The principles are the same.
I understand the language perfectly, and what their purpose is.
What I'm questioning is the actual theory behind using these things as opposed to more standard language conventions.

Why shoud you need to use dim if you are not type-setting?
It makes sense in C/C++ to use
int myint;string s("init");
because you are initialising the variable with a type, but with dim it's simply a redundant keyword.

As for using the single-quote as a comment I don't know why a language designer would go against all standard language conventions and choose that.
Thanks for moving the thread, whoever did. For the record it's not a PHP vs ASP question, I was having a look into ASP(VBscript) to see about learning another web language but some of the design choices seem counter-intuitive.
Not just compared to PHP, but compared to C/C++/Javascript etc.
I've been going over VBscript and I can't fathom why the language was designed as it was.
It wasn't designed as such AFAIK. It just evolved.

First there was BASIC [God bless it!]. Then Microsft produced their own version - QBasic which was included in DOS. That became Quick Basic which was a standalone product. That in turn became Visual Basic, when Windows became more widespread.

Microsoft then modified Visual Basic to run as the programming language for Office, and it became known as VBasic.

This in turn was modified into VBscript for use as a serverside language,

Hence, you will find a LOT of old BASICy things in the language.

There again, I might be wrong!

Anyone still able to program in BASIC? :rolleyes:
I use ASP as I needed to learn it in my first job with an e-learning company. Even though I know PHP is better and more versatile, I can't quite bring myself to learn it for the want to learn something a little more powerful like Ruby on Rails or Java. Mind you, I haven't made much of a dent in either of them.
I'm looking to expand into another language. PHP is great and because it's almost universally supported there's no problem pitching a project in PHP.
However, I'd still like to have JSP or ASP or the like for "corporate" jobs.

Python seems to be on the up at the moment. Despite its unconventional style, the lack of braces does actually improve readability.

PHP is very easy to use though, it's very easy to pick up if you had to modify a script or add to it etc.
daviddoran said:
Why shoud you need to use dim if you are not type-setting?
VBScript only has one datatype - type variant (but has several sub-datatypes). Even still, how would you declare a variable without 'Dim'?
var1 = new Variant?
I guess it could have been do-able but I like the fact that there is something there to help declare variables.
PHP is the better language - on a boring day, I'd go so far as to say it's the only one that deserves the title "language". Problem is that that really only goes for PHP5; PHP3 and PHP4 were really just the unix equivalent to ASP, and as to the pre-PHP3 stuff, it was pretty much just m4.

Put it this way - I took this job to get away from ASP, .NET and VBscript. Yes, you can write maintainable code in both, but VBscript is like Perl without the positive points; it's too damn easy to write bad and unmaintainable code in it. On top of which are all the automated tools that just lump huge blots of computer-written (and damn near computer-readable-only) code into projects.

And on top of that there's the point that ASP usually goes along with MSSQL...
Ah, it was only a matter of time before someone brought up Ruby (on rails).
What I'd be worried about is spending time learning a language that I wouldn't use much or that was hard to deploy because hosting environments didn't support it. Though more and more hosting services support Python/Ruby now :)


New Member
Meh. If you're heading towards J2EE, you're heading towards a whole other realm outside scripting languages anyway.

ps. Java sucks. So does C++. Why we're not all using objective-C I'll never fully understand...
Not open for further replies.
Award-winning Mac antivirus and Internet security software