One Runtime To Bind Them All 479
Sowbug writes "Here's some interesting Saturday night reading: a critical examination of many of the advertised benefits of .NET's CLR (Common Language Runtime) and the other technologies (MSIL, CLS, CTS) that make it possible. It's written from the perspective of a Java advocate, Osvaldo Pinali Doederlein. "
Thats *more* biased (Score:4, Funny)
The obvious solution (Score:2, Funny)
Use an x86 emulator for all non-x86 platforms.
Let's be frank, Windows doesn't run on many(any?) non-x86 platforms so this makes a bit of sense. Instead of trying to design OOP intrinsically into the run-time, why not just agree on a common ABI.
Protection mechanisms can be handled through the run-time library. There really is not need for a CLR that is truly capable of running multiple languages.
That is not what MS is after though. MS is trying to compete with Java. There is no need for a CLR. This article really hits on a key issue.
Different hardware, different languages, and different ABI's all exist because they fit different niches. There can never be a system that handles everything as efficently.
Re:Well, m$ has to do something. (Score:3, Funny)
Very true.
The LOTR reference is hauntingly correct! (Score:3, Funny)
Sounds just like it: Here, use these beautiful new "rings" (.NET), and all will be good. At least until I use my super-powers to control you when you least expect it.