Not only was the IE rendering engine used to render web pages, but the operating system itself, and apps, could call Trident to render HTML and CSS. You may not be aware, but the Internet Explorer rendering engine (Trident) has been an intrinsic part of the Windows operating system since Windows 95. Chrome, Firefox, and Internet Explorer now all support SPDY. At this point, it isn't clear if this is a tacit admission that Microsoft is handing the HTTP 2.0 standard to Google and ceasing development of its own S+M spec. Microsoft presumably chose SPDY because it's more mature and already in use across the web, most notably on Google's services.
S+M is actually based on SPDY, and provides the same kind of speed-up over normal HTTP (on the order 40%). Back in 2012, citing a lack of mobile- and app-oriented features in Google's SPDY protocol, Microsoft unveiled HTTP S+M. The inclusion of SPDY, however, before its own HTTP S+M protocol, is a bit of a puzzler. The inclusion of WebGL, now that Microsoft is assured of its security, is a no-brainer. As we discussed last month, WebGL and HTML5 allowed Unreal and Mozilla to bring the Unreal Engine 3 to Chrome and Firefox - and now Internet Explorer can get in on the action. WebGL is a technology that allows websites to access your computer's graphics card via JavaScript, using a language/API (OpenGL) that developers are well versed in. HTML5 support is also much improved, and some much-needed interface tweaks have been deployed.
In a massive about-turn, after declaring WebGL to be insecure and working on its own HTTP replacement, IE11 will support WebGL and Google's SPDY protocol. Microsoft's preview of Windows 8.1 is now available to download, and one of the most exciting new features is the inclusion of Internet Explorer 11.
0 kommentar(er)
