Having been there, done that with Visual Basic (i literally converted from it to Perl back in February of 2001), i can say that i no longer desire to build applications with Visual Basic (same with .NET). I really liked MZSanford's "lacks heavy lifting features" con for VB, it really says a lot about why Perl is a favorite tool for those programmers who like to get stuff done (and still have some teeth and/or hair left at the end of the day).
I'd really like to add onto this. A few days ago I started in on a project at work. From the specs I could probably write a ten to twenty line perl program, have the problem solved and get back to my other more important projects. But no, I get to do the work in LotusScript (it's Visual Basic for Lotus products. It's 95% identical to Microsoft Visual Basic). Ugh! All in all the things I've found myself needing are a SQL GROUP BY/SUM/COUNT aggregator (except without SQL), hashes, arrays, regular expressions and the spiritual equivalent of anonymous code references.

VB does have hash (called "List") and array support but it's extremely poor. I had to spend a good portion of my time writing some Hash and Array classes so I'd get all the things we take for granted here in perl (untyped variables, push, pop). I substituted VB's Like operator for a regular expression and got my anonymous code references through Execute which is somewhat like eval STRING except that all communication has to be done via globals. All in all I had to work a lot harder to get to (somewhat) the same place as the perl code could have gotten me.

I still don't have a fully functional Array class but I didn't need things like shift, unshift so they didn't get put in. The Hash class works well enough I guess. The Like operator cannot be compared to regular expressions because you lose so much functionality. The code I wrote is inflexible in it's pattern matching support so if I ever need real regex then I can ask the client to go pay $200 for a license to VB Regexpr.

The last bit though - code references I'm somewhat afraid it's not maintainable since I don't think my team has spent much time thinking about eval "". I'm sure they could pick it up but still... it's significantly scarier code than it would have to be if I were writing perl.

I think the net effect is that VB can get you to the same (mostly) place as perl. You just have to work much, much harder and be more creative. Oh and it takes longer as well.

In reply to Re^2: Perl versus VB by diotalevi
in thread Perl versus VB by juo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.