Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re^2: Visual Basic .net and Perl: learn the former; use the latter.

by Anonymous Monk
on May 11, 2015 at 17:09 UTC ( #1126324=note: print w/replies, xml ) Need Help??


in reply to Re: Visual Basic .net and Perl: learn the former; use the latter.
in thread Visual Basic .net and Perl

I have to disagree about not sure what network programming you are referencing, but I use Visual Basic Express to do various task on different servers and PC's. I also used VB to import data to MS-Access, SQL, execute Queries, and even create queries. Don't get me wrong I am liking perl, but I like a GUI. I am working on a VB program to manage PERL scripts at the site I am assigned to. The perl programmers constantly are changing folder paths and numbers in perl scripts and copying them and creating a new bat file. With VB they no longer have to do that. So all languages have a purpose. It is like a Phillips vs flat head screw drivers. They both work, just with specific screws. Non really is better then the other. And sometimes you can use a flat head driver with a Phillips screw, but can't do that in reverse.
  • Comment on Re^2: Visual Basic .net and Perl: learn the former; use the latter.

Replies are listed 'Best First'.
Re: Visual Basic .net and Perl: learn the former; use the latter.
by jonadab (Parson) on May 25, 2015 at 13:57 UTC

    Wow, thread necromancy.

    These days I'm working a lot in C (which I am learning by studying the NetHack codebase; yes, I realize this is a terrible terrible approach to learning C and will no doubt cause irreversible brain damage, but I am doing it anyway) and trying to get around to learning Ruby finally. I still think in Perl mostly, but I now occasionally catch myself trying to write "else if" in Perl instead of "elsif", due to the C.

    The perl programmers constantly are changing folder paths and numbers in perl scripts and copying them and creating a new bat file.

    They almost certainly should not be doing that. There are like fifty different ways to avoid hardcoding paths, and most of them are better than hardcoding paths. Using VB instead of Perl isn't really relevant to this, though: I can assure you that the tendency for programmers to hardcode paths, particularly when they are either A) not very good or more likely B) in a hurry, transcends language. PHP programmers do it. VB programmers certainly do it (and often in a way that breaks in various interesting ways if you try to run the code on a different version of Windows, because figuring out how to use the %BLAH% API really correctly is something of a dark art). Lisp programmers do it. Perl programmers do it. C programmers do it -- or do it in Makefiles, which is just as bad, unless you subject yourself to the agony that is maintaining good .ac and .am files, and then it's still not really good. Ruby programmers do it. Inform programmers don't hardcode paths, but that's because Inform programs don't directly do anything with files at all, so that exception really doesn't count.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1126324]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (4)
As of 2022-12-01 02:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Notices?