Back to the past to see the future (2)

Yesterday read Li Jianzhong TechEd2011 "WINRT" speech, conveniently wrote a little saliva article recorded.

Back to the past to see the future (2)


Winnt has not yet received commercial recognition, WIN95 turned out. The PC World ushered in a big outbreak, more people know that the computer bought a computer to know the WIN95. But with so many new users and new developers, hackers have long coveted the market. So the novice does not use the new developer not to write, thus causes WIN95 often blue screen or freezes. Of course, Microsoft in the security and stability development has not been too much emphasis on the strategic level, so all kinds of Windows instability insecurity was blown out. Gates was forced to do strategic-level requirements, and all Microsoft developers had to learn how to secure coding and stability coding. Of course WIN95 from the DOS, WIN32 this road along the way, the nature of the underlying architecture also has problems, so slow to solve this problem.


Although the WIN2000 replaces the win95,win2000 using the Winnt kernel, the last WinXP that is more easily available also appears. Stability and security seem to have been raised a lot. So, in the past to bring down the blue screen other people's computer hacker virus This will not be easy to put on the strength (think of someone else's computer to make a blue screen crash so it does not really benefit). A new generation of hackers is money worship, and want to be. Where does the money come from, the credit card number, the bank card number, in China there are game accounts and QQ accounts of these valuable things. So hackers moved to the position, just also met the great development of the Internet, we are all online but everyone is a novice on the internet, there are some Trojan fishing cheating is also unfamiliar. So, fewer viruses, and from the Internet Trojan fishing more. So the anti-virus software also transferred the position.


But Microsoft's strategy is not braking, but it is still sprinting for stability and security. Do not let the hacker directly operate the OS kernel directly to operate the CPU, memory, not to engage in memory management and pointer management programmers write the program can also have a certain degree of stability. So. NET and live. There it is. NET virtual machine, for the prevention of indiscriminate development of novice and high hackers are effective. But, in fact, the times have developed too fast, users need to protect the security and stability of the browser, and Microsoft is still operating system to toil.


Although Gates finally realized the importance of the browser, mustered the whole company's development, marketing win the browser century war. The war was over (Microsoft was almost torn down), but Gates and Microsoft were still PC ideas rather than Internet ideas, so IE6 lay in a big share of the market without thinking about improving. When Microsoft once again realizes the user to the stability of the OS security already not to care about and more concerned about the stability of the browser, security, even the compatibility of the website, Microsoft just rush to do IE7. Of course, with Vista's failure, IE7 is also short-lived.


. NET virtual machines have the stability and security features that are not attractive to both developers and users. How about that. Microsoft is looking at application-level technology to attract. such as better asp.net web programming technology, better webservice and XML technology, more support for various development languages, more convenient class libraries and controls. It is now a cumulative addition of WPF, Silverlight, WCF, WF, LINQ, asp.net MVC, Entity Framework, and constantly enhance the vs.net IDE, increasing the application layer technology to glue the developers.


Microsoft has a tighter Windows kernel attached to the kernel. NET virtual machine, on the virtual machine to engage in a variety of application technology. This model is all about PC-level servers, PCs (including laptops), tablets, PDAs (not knowing there are no survival scenarios for such devices), mobile phones, game consoles, home appliances (embedded devices). An OS-all-all device, a virtual machine, IL language, vs.net IDE all development languages.


Now the WIN8 is coming. I always suspect that WIN8 is a WP evolution (Windows micro-core +. NET virtual machines, just as the ipad os evolved from the iphone OS. WIN8 supports flat touch (Metro big button style meets finger press) and PC status (feels like changing a theme skin).


Known as WIN8 in web development or HTML+CSS+JS, local development is the Metro XAML development. Some say Silverlight is dead. Technically, I don't think so, because whether it's WPF, Silverlight, or Metro XAML, the technical nature of the xmal is to describe the UI (just like the HTML description UI) and use the front-end JS to control the UI. This native application model and Web development model are essentially the same technology.


In WIN8 native programming mode, is C + +,. NET language, WINJS can be developed. JS development of local applications. Right. Microsoft is a layer on the WINAPI, so that JS can have the calling interface. But wait a minute, this and JS call Microsoft Local ActiveX what difference. It's not the same.


Again, metadata metadata. It used to be a typelibrary separation of COM code and declarations, just as Microsoft now separates UI definitions from UI controls. Past. NET code is defined and implemented together, now also want to separate metadata. In the past. NET UI programming is also a combination of UI definition and UI, and is now separated.


Remember the past when writing local applications, with the delphi+com write business logic, with Delphi control to write performance layer. When writing a Web application, write the business logic with delphi+com and use html+css+js+asp to write the front end of the display.


Now write the local application, write the business logic with the C#+.net component, write the presentation layer with the. NET control (WPF, WINFORM, Silverlight). When writing a Web application, use the
C#+.net Components Write business logic, using html+css+js+asp. NET write front-end display.


ADO in the past has also been upgraded to Ado.net. In the past ADO are directly connected to the database for additions and deletions, the Delphi has local Clientdataset components, and Microsoft also learned this recruit in the Ado.net also added a similar dataset.


When writing local applications in future WIN8, write the business logic with the C#+.net component, write the presentation layer with the. NET control (WPF, WINFORM, Silverlight), but with the Metro controls, the Metro style, Can be controlled by WIN8 to touch multiple points. When writing Web applications, use the C#+.net component to write business logic and use html+css+js+asp. NET write front-end display, still as usual.


The UI is almost html\css\js\xml, either locally applied programming mode or Web application programming mode. The UI is the interface and definition of the presentation layer.
Define and implement detach, dynamic binding. The essence of definition is metadata
Serious attention to the implementation of design, implementation of the design seriously concern interface design and interface input and output data parameter design, and SOA sca\sdo is mainly to emphasize these two points.


The world's roads are Changshu and call, so technology is no longer the difference and comparison, more is the implementation of the details are as good as you want to meticulous. Often is the reality has the stipulation, has the method, has the execution detail, but the people coming and going often will cause someone to have no idea to have these rules, some people can not understand, some people understand has the deviation erroneous zone, some people may carry on, some people can carry on occasionally, some people have to enforce, Some people feel that these rules do not solve the problem is silly, so disdain to implement. As a result, a good architectural design often in the execution level of the poor deformation. Of course, if the architecture design and implementation design of these upstream links have a lot of problems, let alone code landing execution.