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.
This article is not pro-Microsoft. It's pro .NET. The difference being that .NET are the technologies and software paradigm, and Microsoft just happens to be bringing it to market at warp speed.
Eugenia seems to be very critical of Microsoft as the guardian and caretaker of these technologies because of their dirty business practices and monopolistic tendencies (A computer on every desktop, Windows .NET on every computer). I mean, the STANDARD portions of .NET simply amount to some useful tools. Microsoft still OWNS many other parts, most notably the Passport/Hailstorm gatekeeping data storage whatever which will be the FIRST .NET enabled thingie of its kind to market.
I don't want Microsoft in charge of my information.
So, I say we can't entirely ignore .NET, we just need to find a way to weaken Microsoft's power over it...
This article is not pro-Microsoft. It's pro .NET. The difference being that .NET are the technologies and software paradigm, and Microsoft just happens to be bringing it to market at warp speed.
Eugenia seems to be very critical of Microsoft as the guardian and caretaker of these technologies because of their dirty business practices and monopolistic tendencies (A computer on every desktop, Windows .NET on every computer). I mean, the STANDARD portions of .NET simply amount to some useful tools. Microsoft still OWNS many other parts, most notably the Passport/Hailstorm gatekeeping data storage whatever which will be the FIRST .NET enabled thingie of its kind to market.
I don't want Microsoft in charge of my information.
So, I say we can't entirely ignore .NET, we just need to find a way to weaken Microsoft's power over it...
--JM