SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: JC Jaros who wrote (47613)7/12/2000 3:03:00 PM
From: The Duke of URLĀ©  Read Replies (2) | Respond to of 74651
 
...--- I'd just like to say that if we, on the SUNW thread, had a Sun employee spewing out like,... I for one ...

Say, J.C., I must have forgotten to introduce you to Cheryl? :)))



To: JC Jaros who wrote (47613)7/12/2000 3:31:46 PM
From: david_si  Read Replies (2) | Respond to of 74651
 
JC - "That's the MS compatible re-implementation of Perl, yes?"

No, every one of the languages come from a 3rd party. You should have read the articles.

The .NET platform beats anything else in existence. Don't be quick to judge when you don't have the details. I stand fully behind Mozek's opinions. Since you're criticizing without even having details, your opinion is obviously clouded by bias.



To: JC Jaros who wrote (47613)7/12/2000 6:14:13 PM
From: Andy Thomas  Read Replies (2) | Respond to of 74651
 
well the windows perl from activestate seems to run everything i've thrown at it from the o'reilly books.

does the new .net engine support standard perl such as this or is it some bastardized, msft-specific version of perl?

if msft has left all of the old perl in place but added additional commands, i don't see the problem, as long as it remains quick. if they're deleting standard perl commands and putting in their own... well my first thought is that that would suck.

andy