The Best .net Response I Can Give
Ok, I just finished taking a class on Objects and Design (programming in Squeak... for those who know, ahh!)
But one interesting thing we discussed near the end was the .net framework- what it is, and how it works.
I will try my best to explain what I know, so bear w/ me:
.net is a method of using xml serialization to create 'objects' that have a basic state but no true behaviors. In english, this means .net lets you 'program' by writing xml to define 'objects' but not quite in the true sense of the word, since if you create a class in C++ or Java, the resulting instances of the class would have both a state and behaviors, whereas in the .net strategy xml 'objects' would have their state defined but no specific behaviors that it can use/perform. Sorry, I know that doesn't make much sense.
What this means really is that w/ .net you should be able to rapidly create and deploy classes, and write programs that take up little space, and are easily modified (GUI or otherwise) and updated. In this sense, .net seems like a good idea.
Cons though- there is no way to regulate the xml class files, therefore any joe blow with a text editor can go and edit the xml files, i.e. no file-protection or modification 'blocking', I suppose you could say.
Ok, I am done ranting for now, feel free to correct me if I made a mistake or wrote something incorrectly, and if I can find the lecture slides on .net i'll post the link so you all can read about it and see if I am just plain nuts.
Man, it's late (or early).
Here is the link to the slides:
http://coweb.cc.gatech.edu:8888/cs2340/uploads/1847/NET-framework.1.ppt
Hope it is helpful to all those curious minds.
Related Topic on SOAP (Simple Object Access Protocol):
http://coweb.cc.gatech.edu:8888/cs2340/uploads/1847/soap.html
Enjoy my friends!