.NET
Glory 2002 autumn
"Legacy Software" and "Legacy Programmer" are the maximum resistance of hindering .NET popularization. Another resistance (it sounds a bit vulgar :)) is the current Windows operating system is not pre-installed .NET framework. Run .NET application, you need to install .NET framework, this is a bit trouble. Why COM will quickly succeed in a very short time, and the COM infrastructure built in Windows cannot be said to be one of the reasons.
Microsoft is certainly better than anyone, so the "Windows .NET" series operating system will inevitably refer to the day.
If you don't think about this point, you may want to see Corba destiny on the Windows platform. Of course, this is only one of the reasons, and I said, this reason is a good code :)
However, it is necessary to correct a fallacy. Not in a minority programmer, you must also install the .NET framework on the client machine that is visiting the web page (.aspx) created by ASP.NET technology, this concept is wrong. The truth is actually very simple - the server always returns the generated HTML.
Whether Microsoft claims how .NET does not affect "C # is the .NET Best Language Archive".
But in a considerable period of time, Visual Basic .NET may have more users than C #. The reason is not complex - existing Visual Basic programmers are numerous - although today's Visual Basic .NET is no longer a previous Visual Basic.
Visual Basic programmers transition to Visual Basic .NET, which may be more difficult than transition to C # to C # than C or Java programmers.
The .NET framework consists of a common language runtime (CLR) and .NET framework class library. .NET adds a layer of abstraction over the operating system, .net itself is not an operating system.
Why is there so many people who are abhorlet? This is very puzzled. No matter which company, if you can achieve this achievement like Microsoft, it is great. No matter who sits in Microsoft, it is estimated that it will be like this.
The person who is evil Microsoft is either Microsoft's competitors. Or is it a narrow developer of non-Microsoft camps, or not, pure people are also clouds, and they are jealous.
No matter how much you abhor, no matter how you don't like .Net, if you are a "Microsoft" developer, learn to master the .NET is just a morning and evening.
If you are a Windows developer, even if you never plan to use .NET technology to develop actual software development, it is impossible to completely immune to .NET, you are at least to know how it is.
In the next few years, .NET and Java will form a chamber to fight. The two major camps have support forces, only to learn each other in the competition to move together. It is difficult to eat each other in any party.
In the software development world, the monopole world is inexplicably overbearing, it will never last long; the balance between the two-pole world is difficult to maintain, it is easy to break; the multi-pole world is colorful, but will undoubtedly become the disaster of developers, because of the different The integration of quality technology has never been a nightmare.
Java has occupied a large site, with Microsoft, .NET will maximize the pre-net developers to your arms. In this process, someone may escape to the Java camp, but the number will not be too much. The reason is very simple. If you are a Microsoft technology developer, learning .NET wants to spend the effort, no matter what to learn Java to spend.
In the process of transition from Microsoft pre.net technology to .NET, it will definitely eliminate some developers who can't keep pace with the times, which is normal. In the process of technological progress, every innovation, the disabled is always abandoned. Natural selection, material competition.
How many people will use Managed C ? The number should not be too optimistic. A considerable part of the C programmers often have some feelings that have no advantages, disdain for any non-C , and there is very much, only C high feelings. In the eyes of these C programmers, Managed C is not C , or said, charged, Managed Extensions for C is not only a .NET patch that Microsoft is playing with C .
Each of the rigorously in line with the language of the .NET framework will eventually be converted to a MSIL code (of course, some languages only provide the ability to interact with the CLR-BASED code, do not generate MSIL), but this is not It means that the same code written in different .NET language will be converted to the same MSIL code. The quality of the compiler will differ, and the quality of the generated MSIL code will certainly differ.
Non-Soft .NET language is said to have two hits, but they are difficult to become mainstream. Some third-party .NET language practical significance, but it provides a way to transplant existing code to .NET, others only have the value of academic research.
I don't know how many people will use Perl or Python on .NET, although today they have no one is not a few. I can only affirm that Delphi (Object Pascal) should be an exception.
Can you become a mainstream .NET language, depends on: Is there enough "legacy software", have enough "legacy programmers", is there a good idea, whether there is a strong strong organization to provide strong support .
Or only Microsoft's own technology can be best matched with Microsoft's technology, COM is an example. COM is undoubtedly the most successful cross-language mechanism in the pre.Net era, but this technology is in the microsoft's own language (exactly, it is a development environment), such as crossing Visual C to Visual Basic and the opposite, Sprinkting to other languages (development environments), such as Delphi, will expose such or such problems.
I would like to have a similar situation not happened to .NET, I would like to follow the language of CLS, I can be freely seamlessly interoperable, just like Microsoft's home student. Net language :)
Web Services technology is not Microsoft, nor by .NET, but still has a considerable number of people mistaken to think that it is a technology that is accompanied by Microsoft .NET. Microsoft Extension Technology (Concept) Kniff, thereby visible.
Don't misunderstand, .NET Compact and .NET framework can be said to be very different. .NET Compact is not simply cut off some things from the .NET framework, otherwise .NET Compact will not be proved than the .NET framework for later delivery.
The ASP.NET application is the .NET application. Ordinary ASP developers transition to ASP.NET's pain, which will not be able to get from Visual Basic to Visual Basic .NET. Where is it?
ADO.NET is a revolutionary technology, although it is undeniable, it borrows many data access technology from Borland, but ADO.NET supports XML technology, which is undoubtedly leading. I hope that the speed should not be a resistance to Web Services being widely used. In a test application prepared by glory, the application effect of Web Services from different vendors is surprising, but this application speed is slow, and it is unexpected.
Perhaps Web (WAN)-based distributed calculations, forcing us to make a speed compromise, just like we can tolerate (and habits) browser applications than traditional Windows GUI applications.
The .NET Framework Application may be slower than those Windows DNA applications, but we really should care about how fast these applications can run, but they are so fast, fast to meet user business processing requirements.
Java's success has provided these evidence. Although Java code is generally slower than the local code, it is still enough, many organizations use this technology very successfully. Therefore, it is entirely more than the concerns of .NET speed. According to Microsoft's own statements, some test data provided by third parties, .NET is at least more efficient than current version of Java.
After all, the quality of hardware is constantly improving.
