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
I think Apple's approach to .NET makes alot of sense at this point. particularly in light of the still open ended conclusion that .NET will dominate development on Windows.
The truth is that I believe there will be a balance. The CLR is still a runtime, and therefore will be slower than native code. At the same time, WebServices will quickly replace COM/COM+. This is a good thing. And since WebServices are now standards based. An application written in Java or Objective C, using SOAP could attach and use a web server, giving you the advantage of native code or the JVM, while still allowing you to leverage the Windows world.
Apples's best bet today would be to make certain the they have integration code in place, and worry about implementing a native .NET framework only as needed.
Besides, if MS continues to bring Office to the Mac, chances are that MS will do the bulk of the work for Apple. Combined with the work that Corel is doing to build a BSD version of the .NET framework, Apple looks to get 80-90% of the way there without expending a dime.
Sounds like sound business planning to me.