Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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: Andy Thomas who wrote (47640)	7/12/2000 6:30:43 PM
From: JC Jaros	Read Replies (2) \| Respond to of 74651

You're throwing snippets of code at it, Andy? You'll note that "the O'Reilly books" are of two different types: Perl and Win32 Perl. If o'reilly is publishing two different versions of the same title (ie, Learning Perl and Learning Win32 Perl), you gotta suspect that maybe activestate doesn't exactly run the same stuff. There are plenty of examples of Perl programs that don't run Win32 Perl. --- If you're programmimg Perl cross-platform, you're the first guy I've met doing it. -JCJ

To: Andy Thomas who wrote (47640)	7/12/2000 7:23:33 PM
From: mozek	Read Replies (1) \| Respond to of 74651

if they're deleting standard perl commands and putting in their own... Doubtful. Perl is an ActiveState project, not a Microsoft project. The fact that there really are other companies putting their own languages on top of the .net runtime may be a bit hard to accept for those used to a language restricted world, but it's happening. As far as performance, now that the environment is publicly announced, I can give you my opinion. The .net CLR (common language runtime) screams. I think it will be shown that most languages, which depend on a runtime, including script or compiled languages will run faster if moved to it. Languages like C and C++ in the hands of great developers will probably not benefit from a perf boost, but will from integration with other languages, leveraging of a common framework, and super simple access to all of the .net services. Of course, that's not to mention the fact that you won't need separate runtimes for Perl, JScript, VB, VBScript, C#, C++, or other languages that target the environment. That alone can save working set and eliminate redundancy. Finally, when Microsoft or others improve the .net environment, all .net languages benefit. I'm sure more detailed information will be available from other sources as the PDC information sinks in. Mike