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.
>> The CLR is still a runtime, and therefore will be slower than native code.
From tests I've done comparing VB & VB.NET and C/C++ with C#/C++.NET this isn't true. The initial startup of an app. is slower but then, depending on the operation (i.e. whether you stick within the .NET Framework or not) the performances are comparable.
>> At the same time, WebServices will quickly replace COM/COM+.
Not really, most people use COM/COM+ in an internal environment and Microsoft have been fairly honest that Web
Services will *not* out perform these technologies in such cases. Web Services are aimed firmly at outmoding technologies like CORBA; widely distributed RPC.