in reply to Perl versus VB

Alas, I program on a daily basis with both Perl and VBscript.

I find that VBscript is useful for ONLY the most trivial applications, due to:

Perl now, feels like I'm driving the Monorail. It's sleek, robust, and easily takes me to where I want to go. (sorry for all the Disneyland analogies...)

I find that I can prototype things quicker, and I never run into language limitations. I can't count how many times I've started coding something in VBscript, only to trash the code and redo it in Perl.

The other confusing thing about M$ is that things just don't work like they're supposed to. Regexes, subroutines, modularization, etc., just feel wrong (weak, unnatural, <insert your favorite pejoratives here>)

Where do you want *them* to go today?

Replies are listed 'Best First'.
Re: Re: Perl versus VB
by Wysardry (Pilgrim) on Jan 18, 2003 at 01:49 UTC

    I have to point out that VBScript is a severely limited subset of Visual Basic. It would be fairer to compare VBScript with PerlScript, or Visual Basic with Perl.

    Which brings up a point that nobody else has mentioned so far - Visual Basic is not suitable for use in programming Web applications.

    That's a severe limitation for most people these days.

      um, actually, perlscript is exactly the same as perl, except that it supports ASP-like <%..%> syntax. so there you go.

        Perhaps I should have specified client-side PerlScript versus VBScript.

        Server-side PerlScript seems to be fairly pointless unless the author has some sort of phobia against coding without ASP/Cold Fusion style tags.

        ActivePerl does need to be on the system too, after all.