Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?

Windows, .NET and a language named Perl

by Anonymous Monk
on Apr 17, 2001 at 01:26 UTC ( #72960=perlmeditation: print w/replies, xml ) Need Help??

Those of you who took a look at the .NET specs from

What do you think? Will .NET help Perl to make a new stand
on the Windows platform? Will it be of equal speed as C#
or C++ through the Common Language Runtime?
Or will it fill miserably and stay where it came from.

I am just curios what you think.
  • Comment on Windows, .NET and a language named Perl

Replies are listed 'Best First'.
Re: Windows, .NET and a language named Perl
by lzcd (Pilgrim) on Apr 17, 2001 at 02:39 UTC
    I can only imagine the fun and joy that ActiveState are having squeezing perl into the .Net world but I digress...

    On the people side, my suspicion is that the common .NET runtime libraries will help bring quite a few Perl programmers into the same development groups as the current C(++) guru's.

    This still doesn't remove the bigger "future skills" issue that many managers have with ‘peripheral’ languages such as Perl but it go along way into allowing perl code (albeit .Net compiled) to go deeper into the Win32 world.

    Side Note: The “future skills” argument, for those who’ve yet to experience the joy runs something along the lines of the following: “Sure Bob here can do wonderful things in perl (on the side of his normal VB stuff) but what happens when he leaves? Our company is focused on VB not Perl. Why shouldn’t we keep all of our stuff in VB thus ensuring anybody in the group can maintain the code base”. I tend to regard it as a fairly good argument, having enjoyed some of the earlier choices in languages myself (Progress Version *6* anyone), although I wouldn’t suggest it was unbeatable.

    On the pure technical runtime specs, I think it should do pretty well. In a pure .Net environment I suspect it’s performance won’t be that different to it’s (distant) VB cousins. As the bulk of a .Net programs time seems to be interfacing with other objects, I’m leaning on the side of “Who’ll notice?”.

    As with all these type of debates, some will make comparisons to stand alone, C++ that’s been tuned to within an inch of its word length and some old assembly code that does nothing short of fry half the mother board with it’s impressive floating point calculations but…
    All of this means didly for 95% of your avareage business applications.

    The bulk of business code tends to revolve around making sure that things go according to the business logic plan (and not to TCP/IP rather strained melodies for example. <g>). While there certainly are components out there that do contain a plethora of complicated string and mathematical manipulation, it tends to be the exception rather than the rule with production code (IMHO).

    Where was I going with all of this… I have no idea… but I feel a little more sedated now… might even put down the axe now…

    Thank you for your window suckering time

    PS: I'm placing my faith in mankind here that this question was something better than troll bait for those hovering over the -- button.
      I find it ironic that the first post I have seen for a while that suffers from Microsoft's non-standard extensions to ASCII is devoted to how Microsoft's new initiatives will drive Perl farther into the Win32 world...

      My main fear with .NET is that Perl on .NET will be subtly incompatible with Perl everywhere else. I don't mind it so long as it remains portable.

Re: Windows, .NET and a language named Perl
by arhuman (Vicar) on Apr 17, 2001 at 11:04 UTC
    It's the same old story :

    The claim :
    With our new framework (previously VM) you could code in the language of your choice (previously Java)
    and see it works without translation on any platform supproting our .NET framework
    (previously our Java Virtual Machine)

    The Facts :
    It's as always the portable language myth (as old as ANSI C)used and abused by PR people to capt a market
    that they'll hold captive later by introducing subtle change to make their portable framework incompatible with any competitor (as tilly already pointed out...).
    Just add refurbished buzz words : ASP,SOAP (Instead of previous clients/server or thin clients...)
    and you got a 'marketing killer Idea'.

    My opinion :
    Why not ? let's them developp all their stuff, there will be (as always) good things to pick-up.
    But Let's not be naive to believe that Microsoft has suddenly changed its strategy
    and has became an interoperability devot worrying about the developpers needs/desires.
    Anyway, stay aware, and support open-source for it's the best way,
    to my mind, to counter those silly tactics...

    "Only Bad Coders Badly Code In Perl" (OBC2IP)
Re: Windows, .NET and a language named Perl
by Starky (Chaplain) on Apr 17, 2001 at 09:19 UTC
    I don't think that it will bring a tremendous new surge of interest in Perl from the Windows community, but it is necessary to maintain the current level of interest given the weight Microsoft is throwing behind its .NET initiative.

    The Microsoft world is not friendly to those who don't jump on Redmond's various bandwagons.

    I do hope that if .NET can truly create the language independence that Microsoft thinks the world craves, many VB programmers will slowly come to realize that Perl is easier, more intuitive, and a heck of alot more fun than VB ever was or ever will be.

    Massive conversion would be unlikely, in my opinion, given that Microsoft will never have control (i.e., make massive profits from or be able to appropriate) the Perl community and will continue to strongly promote VB amongst its devotees, but wouldn't it be wonderful :-)

Re: Windows, .NET and a language named Perl
by rchiav (Deacon) on Apr 17, 2001 at 19:18 UTC
    I think that the fear of Microsoft trying to make Perl "extensions" is a valid one given Microsofts history, but the .NET framework is much different than past situations.

    All of the things they've "extended" to make propriarity were in an attempt to lock people into using just their platform. I belive that the .NET framework does this, not any language. From my initial impressions on what they're doing, they are no longer trying to make the development language or a client side scripting language their leverage. The implementation on .NET is just too different for things to be portable no matter what they are written in.

    It looks like you're going to use Perl/C/C#/etc.. to manipulate and define your .NET environment in a sense. So it's not going to be at all portable since I don't think Microsoft is ever going port this platform to *NIX systems. It will still probably be Perl as we know it, but the actual code will have no use outside the .NET framework.

    Anyway, that's my $0.02

    Addition: I think it will be similar to how Perl is used in ASP and .wsh files. Example

    You could use Win32::OLE or use objects that are pre-defined to ASP and WSH like so..(WSH version)

    <job> <SCRIPT LANGUAGE="PerlScript"> $x = $WScript->CreateObject('Excel.Application'); $x->Workbooks->Add; $x->{Visible} = 1; </SCRIPT> </job>

    So it's Perl, but Perl using methods that are specific to the environment. Though you could do it using Win32::OLE, I'd assume that anyone working with ASP and WSH would use the built-in functinoality.

.NET is made of people! It's people!
by Sprad (Hermit) on Apr 17, 2001 at 19:42 UTC
    I looked at the MS pages regarding all this .NET nonsense, but I can't make head or tail of it.

    Imagine running on a treadmill while trading stock on your handheld computer and having your cable box make you some toast and coffee! .NET will bring this to you!

    Can anyone cut through the marketing blather and give me a nice, short, buzzword-free explanation of just what .NET really is?

    I'm too sexy for my .sig.

      Read this article from MS. It does a better job of explaining it.


        So that is what Microsoft says it is.

        Do you believe them?

        Take for instance the item in there about building block experiences. Their login piece already has been described. They call it Hailstorm. Now to hear them talk about it, it is going to be the best thing since sliced bread.

        However this is the company that does its best to wipe out everyone else by fair or foul means. It has repeatedly wound up in anti-trust court, generally for good reason. As the old saying goes, fool me once, shame on you. Fool me twice, shame on me.

        I do not trust Microsoft.

        In fact here are my thoughts on what Hailstorm is intended to accomplish. This is not a company that is known for doing a good job on keeping data secure or private. Its track record is, in fact, abysmal. I would be willing to lay money that if its strategy takes off that in a few years everyone will be complaining about its abuses of the power that it grabbed with .NET.

        Besides which, Microsoft's claims to portability notwithstanding, their strategy has always been to make their own platform the first among equals. .NET will, promises notwithstanding, be a Microsoft first platform. Given how Microsoft has abused every other standard to achieve lock-in, what makes us think that they will do differently this time?

        And when it comes to portability, well .NET is a new VM, and Perl on .NET will have new and different bugs from the current. Glancing at what ActiveState has to say, their initial idea of compiling Perl in the .NET runtime was too slow. (Perl is a VM, on a VM?) Instead they have a cryptic comment about a native implementation having to wait for progress on Perl 6.

        Given the design of Perl 6 into a front and back end, I suspect that this means that they are intending to try to map Perl opcodes as much as possible onto .NET primitives and get their own .NET implementation. I am sure that such an implementation will turn out to have behaviour differences from the usual. This is on top of the usual bugginess that I expect from Microsoft products.

        Oh well. At least ActiveState gets some money for this work. And Microsoft's hopes notwithstanding, my belief is that Microsoft is not in the same position that they used to be to force things down the throats of industry. Unless they do something interesting, fast, they will lose hope of locking down the embedded industry, and I think that networked devices (which are rapidly heading towards Linux) are going to be a lot bigger area of growth than PCs...

        so here i am,

        going to the site you suggest, because i would like to know more and i keep getting forwarded to a "smart" 404 page. So rather than that, i try going to to see if there are any links there that might get me where i want to go. Funny enough, check out the graphic in the upper-left hand corner.

        Now, i find this strikingly amusing, since the name microsoft(tm) is so well known that every school child knows how to spell it. Except that someone did misspell it. On their home page. i'm still waiting for the page to load. Did it get hacked? No, doesn't look like. i know it's nitpicky, but with a company as large as Microsoft, they can't afford image loss, even over trivial matters. Or so i guess.

        Anyway, thought that was amusing. As a note, it appears that information loads fine here.


        update: Hmmm, that's not a graphic, it's text (my curiosity got the better of me and i looked at the source). The misspelling isn't as painful if it's only text (considering the thousands of lines of text they have to input manually)...

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: perlmeditation [id://72960]
Approved by root
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (3)
As of 2020-08-11 04:12 GMT
Find Nodes?
    Voting Booth?
    Which rocket would you take to Mars?

    Results (58 votes). Check out past polls.