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
There will always be a need to write code for specific devices. And these devices will always need stable, robust OSes. Just because the programs that run on these devices want to exchange data via XML, they don't have to use the .NET framework. In fact, they won't, because the .NET framework is just M$'s attempt to fix their horribly b0rked API.
I can write a PHP app that will allow RPC via SOAP very easily; likewise with C, LISP, or whatever other programming language I choose. And it has nothing to do with .NET, or whatever stupid name M$ has decided to call RPC this week.
If exchanging data via XML is the future, so be it - but don't get your panties all in a bundle over this silly article. The .NET framework is an attempt to simplify the ridiculous amount of spaghetti code Windoze developers have to deal with..NET My Services is RPC via SOAP, and nothing more.
Oh but wait, we can't resist it - didn't you read the article?
Don't listen to Eugenia's FUD.