Personally, I just love that they have:
if ($Conn eq undef) {
$val = 'undef';
} else {
$val = $Conn;
}
in their example. So sad. But so funny. But so sad.
------------
:Wq
Not an editor command: Wq
| [reply] [d/l] |
January 22, 1999
That probably makes it more "What MS thought of perl" :)
Still, it's an interesting article, thanks.
| [reply] |
| [reply] |
Nice to know M$ approves of Perl.
Not like those of us who use Perl are going to stop just because M$ decides they don't approve.
But the end does give me a good idea on their real opinion, "go ahead and use Perl, if you must, but our products are so much better because we support them."
Personally, I'd tell someone to use Perl over VB and VB script any day. M$ may support VB, but the entire programming community supports Perl. My money is with the rest of the programmers. | [reply] |
This is old news but it may be new to rupzperl.
I have used Perl for as the scripting language for several pre-.NET ASP intranets, dozens of Windows Script Components, and several generators for VB/MTS/COM+ work. Yes, I will confess to having worked with VB. :(
Perl always served brilliantly in these roles. VB, VBScript, and JScript were often too anemic for many jobs. Writing Perl for Windows tasks seemed ticklishly subversive, too.
When the referenced article came out I was happy to see that there were developers at Microsoft (not necessarily MS itself) who were giving Perl its just due.
Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"
| [reply] |
In the last question, "Should I use Perl instead of VBScript?", check out the last sentence:
"If you are a Perl developer already, then I think you already know the answer."
Now, call me a conspiracy nut, but the way I read it, the author is intentially vague, and this is written tounge-in-cheek. I think there is a very real possibility that this fella works for MS, but if you asked him off-site, he might prefer perl.
Re-read the end, and see if you don't agree. | [reply] |
Still it is a good article to email the PHB to get them to ease up on your use of software that doesn't seem to meet their technology strategy. Even if it does most of the work.
"No matter where you go, there you are." BB
| [reply] |