. Net community quarreling (2)

This is the counterargument of Visual C # product manager Dan Fernandez. Just translate rough. http://blogs.msdn.com/danielfe/archive/2005/02/22/378343.aspx

1. counterargument against. NET Framework that is too large and weighs 25 MB

Maybe I'm a little real, but. Net framwork is smaller than 23.7m.java, but there are also. netProgramMore refer to clients or public clients (meaning they are not in the firewall). For example, if you install. NET Framework on a server or on a LAN, there will be no problems. Even on the public client, many shared components from some to RSS readers need the support of. NET Framework. I have talked with many developers who share components. They do not use Java. Many developers use C/C ++, VB, and Delphi. In fact, many developers have downloaded the. NET Framework.

2. Design of. NET Framework

If we use a simple program to determine the similarities and differences between different languages, it would be too minor.

For (INT I = 0; I <X; I ++)

{

......

}

Can you tell the language you wrote? If you answer C, C ++, or Java, you are correct.

3. About. Net Support interfaces, but prefer to use classes

Interfaces are everywhere in the. NET Framework. Interfaces play a more important role in C #, VB, a single-inherited language. Even simple strings have icomparable, icloneable, and ienumerable.

We do not have a mechanism we prefer. We only provide guidance that developers can develop in a suitable way. Our demonstration and practice teams provide guidance and best practices. In this case, I did not find any class implementations that are more inclined than interfaces.