in reply to Visual Perl & ActiveState

Time to bring a little bit of sense to the discussion. The IDE is an addin that Microsoft has no hand in. Its like a new mode in EMACS. THIS DOES NOT EFFECT THE PERL LANGUAGE I'd hazard a guess that the reason ActiveState is involved with Microsoft is that Microsoft likes to maintain some (Low though they be) standards in their products and it's better to work together than ActiveState producew something that causes Windows to Crash even more and Microsoft get the blame. Also this should be viewed as an important Perl advancement as with the still rising popularity of Python on Win32 Perl may end up being a niche market. Without advances like this Perl will flounder Dean

Replies are listed 'Best First'.
RE: RE: Visual Perl & ActiveState
by BBQ (Curate) on May 31, 2000 at 20:48 UTC
    > causes Windows to Crash even more and Microsoft get the blame

    I'm sorry, but the phrase above makes it sound as if Microsoft had no part whatsoever in creating BSODs... I'm an NT Workstation user, and while I'll admit that it is 100 times more stable than 95/98, I can't help but think that this is because I'm typing on a VMS with a new shell. Even with this relative stability I just mentioned, there is no one but Microsoft to blame when Excel or Access crash on me. There's no excuse (except for hardware failure) for a program to crash, IMHO.

    I have seen some good products come out of Microsoft. I think IIS is anoying as hell, and I personaly wouldn't use it, but I can't help admitting that I think its a good webserver. The same applies to the Proxy suite. Sure version 1 was sucky, but they made ammends with version 2.0. That's a pretty good product. All they really need is to get their act together with the OSs and applications.

    You wanna know what MS products I love? Keyboards and Mice! That Intellimouse with the wheel kicks ass when changing weapons in Q3A. :o)

    #!/home/bbq/bin/perl
    # Trust no1!
[reply]

In Section Meditations