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
The idea that the .Net byte code is "JIT" converted into native byte code once and remembers it for future use, sounds good to me as oppose to Java JIT-ing every time.
But I'm use to writing software for a specific CPU/OS combo. Does this mean that I can't optimize .Net apps to be CPU specific in order to get the best performance? And what about inline assembly? I mix assembly code with my C++ code in many areas, and it will be hard to give it up to switch to .Net