It's time to get to know IE again and see ECMA Script 6 results

No one can forget the glory of IE6, but with the rise of the Webkit system, the original development team was split up to other products of IE began to be consumers considered "card, slow, ugly" symbol. Finally, Microsoft began to create a new Edge engine for IE. At least from the data, it's a monster.

Edge has been formally tested in the latest Windows 10 developer preview, and developers can try or debug the new version on devices such as IOS, Android, and Mac OS X via Remoteie services.

In the previous desktop and Windows Phone version of IE11, Microsoft has done a similar attempt to allow the browser to be compatible with part of the Webkit API. And Edge can be understood as the complete form behind this compatibility, it is not only to Webkit to make compatible and collect, but also for the latest Internet standards to provide active support. However, according to the MSDN documentation, the compatibility mode with the Edge comes in for a long time, but is theoretically enabled only when browsing the Compatibility List site and opening enterprise mode. For web browsing beyond this, the Edge provides a way to help users gain a better compatibility and browsing experience by transcending the previous browser UA pattern. Edge provides a universal UA field to adapt to the current mainstream web site, allowing users to avoid the individual identification of the old version of IE content to get the normal Web page.

The IE team would like to rely on the Edge of this adaptation and compatibility to allow users in the future completely out of the "enterprise model" this compromise solution. At the same time, they will continue to follow the various Internet standards and other browsers to ensure that IE can keep abreast of changes in the market. According to the previous message, IE will introduce new UI, new plug-in mode, and speed up the upgrade progress. Combined with the above Edge information, the new IE to the average user experience will be very close to the current Chrome and Firefox.

In addition to being close to mainstream browsers in the user interface and functionality, IE is also trying to bring similar experiences to developers, and the new version has been able to adjust the experimental feature settings by typing about:flags in the address bar. At the same time, the new Edge kernel adds a lot of developer-required feature support, details can be viewed in MSDN.

Of course, before the Edge, Microsoft in the IE10 and IE11 era has given similar comments, only to see the MSDN opinion may not be very convincing. However, the latest ECMAScript 6 compatibility settings can provide some intuitive evidence of this information to some extent.

Is it possible to return to the IE team of IE6 Times to help the new browser, which has barely survived the antitrust?