Linked by Eugenia Loli-Queru on Wed 20th Feb 2002 18:45 UTC
A lot of people have trouble understanding what .NET really is and what its goals are. Mostly because Microsoft has done a good job of confusing everybody using terms that are not self-explanatory or with terms that mean more that one thing. This editorial will present my thoughts on .NET, what it really is, what its motivations and goals are, and why it is the next "big thing." Should we embrace it or fear it? Both, I daresay.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
According to Microsoft, The JIT in .Net could (can?) automatically detect the processor it is runnimg on and just in time compile and optimize at loading time for that specific processor. If it is actually implemented, it means that instead of choosing at design/compilation time the processor you want to favor, you let the JIT decide at loading time. Every machine gets the best performance. Pretty powerfull... if it actually works (don't know, I did not test it).
Mixing assembly and .Net code. Well I don't think it is the idea but I do not really now.