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 |
