Some observations on Windows.NET and VisualStudio.NET in "reprint"

Visual|window reprinted from the "Rain Forum"
Original: Software_young
----------------------Reprint started----------------------------
The purpose of this article is to raise some discussion about windows.net and visualstudio.net, therefore, if the content and structure of this article can not be engrossing or laughable, please haihan.

One. Microsoft's. NET strategy is Microsoft since its inception the most ambitious projects, but also the industry in recent years a rare big, the results for Microsoft and the industry will be decisive. If successful, Microsoft will build a huge advantage for UNIX and Java, and if it fails, it will be the swan song of Microsoft.

Two.. NET's design objectives:
Design a large software service system based on the Web, platform independence, including multiple levels of goals. It is a web-centric, organization of various services, so that Microsoft's client and server-centric com/dcom/com+ into a variety of web-centric services, become a huge web ASP (application service provider); NET and host operating system, the relative independence of the platform, so that it can not only apply to the traditional windows, but also can be applied to UNIX systems and embedded systems, and even handheld devices; a variety of user front-end, including handheld devices, embedded systems, traditional desktops, and even traditional host, will be their customers;. NET includes support for multiple levels of goals that meet the needs of various market segments from handheld devices, embedded systems to 64-bit high-end servers.

Three.. NET's impact:
If. NET success, it will allow Microsoft to invade the traditional relatively small flanking market, through Microsoft's huge installed capacity, a large number of off-the-shelf applications, a large number of user groups generated by the market shock, in a domino way to destroy opponents. In order to establish the modern High-tech market of Mongolia's great empire. This can be seen from the recent fall in Palm and Pocket PC victories, the Xbox market performance and the changes in Microsoft's and Borland's power.

Four.. NET, the power of the structure:
Traditional Windows is built on a variety of services on top of the kernel (you can discover the various service features by looking at each version of Windows NT). A large number of functions into the system core, on the one hand, improve the integration of the system, on the one hand, the system is very large, so that the performance and stability of the system has become a problem, making it difficult to enter different market segments, while limiting the performance of simple applications. The performance advantage of Linux in some applications is precisely because it is relatively simple and less functional.
. NET design, its various functions are decomposed from the operating system, through the combination of different functions to correspond to different market needs, each version of the windows.net is actually different parts of the various combinations. It could be said to be the first operating system in the world to be designed entirely with part models. This, in fact, has started with Windows XP.
The power of Windows XP is not that it has a beautiful user interface, and a variety of tools that benefit the user experience, such as MediaPlayer, but the set of services and architecture it provides. About the service set, you can compare Windows XP and Windows Professional to discover how much new services Windows XP offers and the goals that these services target. On the architecture, Windows XP has been able to remove its graphical user interface and work in a system-embedded way. This means that its graphical user interface has actually left the kernel of the system and become a component that can be assembled. This is a very important change.
Windows.NET's structure, in fact, should be divided into two parts: Microsoft proprietary platform and portable parts. The former includes hardware-related parts and the traditional Windows market, while the latter forms the essence of Windows.NET, which will be gradually simplified over time, and the latter is becoming more and more intensive.
Currently, the. NET support components running on UNIX are under development. If you can succeed,. NET will be able to run on Unix as part of Unix, and Unix will become a host system, just as UNIX is a host system in Java.
If the software under the host system is strong enough, the same can form an operating system, at least a powerful software layer, the former example is today's Oracle 9i, you can see how far it is from the operating system, which is oracle in the market is a great power, but also a host system nightmare , the latter example is Microsoft's Office,office is not only its ease of use, but also its contained visual Basic for application, which makes office a software platform, which is IBM's Lotus Office and Corel's perfect office are unmatched in any way, and their failures are inevitable.
In this way, the traditional UNIX will gradually be Amoy empty, become an empty shell, and eventually die. So. NET's design structure makes it a modern Trojan horse.

Five. About VisualStudio.NET.
VisualStudio.NET is a development tool for windows.net. The huge difference between it and the previous generation has been the object of contention and concern.
Visual Studio 6.0 was designed based on com/dcom and later joined COM +. It is designed with the native software as the goal. Software development directly generates platform-related code. The levels and functions of different programming languages are not the same, and the platform-dependent code is generated directly. This makes binary-level porting virtually impossible.
The design of VisualStudio.NET is entirely web-based service and application. It is actually designed in the form of a virtual machine, and the CLR (the common Language runtime Environment) forms its foundation. Software development generates the middle code, which is converted to the corresponding machine code in the actual runtime, and the benefits of this design are similar to Java, a theoretically unlimited portability. But Microsoft's uniqueness makes this ideal closer to reality.
The CLR is accessed by different programming languages. The ASP has more goal-oriented features, and Visual Basic is actually the first real-world target-oriented programming language. Various programming languages are oriented to the CLR design pattern, making the CLR, rather than the various programming languages, the center of Development. For the first time in history, the choice of programming languages has become a personal hobby and not a goal. I wonder if this sounded the death knell of C + + on the windows.net market?
VisualStudio.NET actually prepares different parts for different market segments. Standard visualstudio.net for standard desktops, server markets, and embed visualstudio.net for embedded markets, a small visualstudio.net, much like visual The relationship between basic and VBScript.
VisualStudio.NET's work is based on the CLR, XML, and SOAP, which are still uncertain, adding some variables to the future of VisualStudio.NET.
The various languages in the visualstudio.net are very different from their previous generations. VisualBasic.NET is almost completely redesigned; Visual C + + is also very significant, although the language level has not changed much, but its class library is completely redesigned; C # is a new programming language, which is close to Java, but only formally, I think, It is a better Java than Java, and is the least burdened, most easily integrated with the CLR programming language; As for java.net, I don't see how useful it is in addition to continuing to support the original Visual J + + user and porting Java programs; when it comes to porting Java programs, I think it's not easy, after all, the incompatibility between the two architectures is much greater than the similarity of their language.
Undoubtedly, VisualStudio.NET is a tool for the development of Windows.NET, but its great difference from the previous generation and the result of the new learning of the developers make people have some doubts about its acceptability.
To be honest, visualstudio.net makes almost all Windows software programmers a beginner, and of course the starting point is not the same. This is why I emphasize the idea of technology, not the details of technology. Technology can not be without details, but too focused on detail, in the always changing it market, will put people into nothingness.
By the way, my hobby is history (real history, not random politics), not software technology. People should have some sustenance, can not finally be the end of the half-baked, to the end of the monastic.
Sorry, it's too far. Thank you, everyone.


Software_young Editor at 2002-02-01 13:47
----------------------Reprint End----------------------------