21. ํ์ค ๋ฉค๋ฒ๋ก์จ์ ํ๋ W3C ์ํน๊ทธ๋ฃน ์ฐธ์ฌ HTML5 Working Group, DOM Working Group, CSS Working Group, SVG Working Group, WebFonts Working Group W3C ํ ์คํ TF ์ฐธ์ฌ SVG Testing Taskforce, HTML Testing Taskforce, Accessibility Testing Taskforce 21
Seeing the decline of Internet Explorer 6 and the steady increase of users choosing to upgrade to Internet Explorer 8 is fantastic. We have recommended upgrading from Internet Explorer 6 to Internet Explorer 7 and now to Internet Explorer 8 for years. We will continue to support Internet Explorer 6 with security updates, that's just one of the responsibilities of Windows. We are excited to get users upgrading fromInternetExplorer 6 to Windows 7 and Internet Explorer 8 and then on to InternetExplorer 9. I want to thank you for being part of this movement.
And that brings us to today. We heard from you wanted more transparency around the builds as weโre delivering them and thatโs been why weโve been shipping the Platform Previews, providing an early, and frequently updated look at what weโre working on. Weโre now on our third Platform Preview release, and weโve achieved our commitment up providing updates about every 8 weeks. The Platform Previews install side by side with your current Internet Explorer installation, and arenโt meant for day to day browsing, but as a place to play and experiment. Thatโs why you donโt see an address bar, or back or forward button.
Welcome!My name is [Insert Your Name Here]. Over the next hour or so, Iโm going to take you through some of the new developer oriented features in Internet Explorer 9. Weโll take a quick look at how IE got to where it is today, what weโre doing to make sure Internet Explorer 9 is fast. Weโll look at what โSame Mark-Upโ means, and how using hardware acceleration to do GPU-Powered HTML is going to make your sites super fast, without changing your code.
Letโs take a look at what weโre doing to ensure Internet Explorer 9 is fast. And I mean fast!
In the early days of the web, there was lots and lots of HTML and only little pieces of script here and there, and an interpreter was good enough for that. Over the years, different browsers have added JITters helping code run faster. But thereโs a problem โ the amount of time and energy that goes into managing the time and scope that the JITter operates in. Basically, users wait. Users have to wait if the JITter JITs too much because the JITter is sitting there compiling the code, and you don't get to run it. The user has to wait if the JITter JITs too little because then the JITter did a little bit and the user is stuck running a slower interpreter.
Our approach is to use modern PC hardware to its fullest. Chakra, our new ์๋ฐ์คํฌ๋ฆฝํธ engine is different from the other engines out there. When Internet Explorer hits ์๋ฐ์คํฌ๋ฆฝํธ, it immediately starts interpreting it, but at the same time, in parallel with the IE process compiles it in the background. As soon as the compiled version is available, Internet Explorer switches over to that. No longer are you waiting for the interpreter or JITer โ your machine is put to good use running the Web faster, without having to make any changes to your pages or code.๊ตฌ๊ธ ํ์ด์ดํญ์ค๋ one CPU Core
Let's talk about ์๋ฐ์คํฌ๋ฆฝํธ in particular. WebKits.org publishes a benchmark called SunSpider. Let's see now IE 9's new ์๋ฐ์คํฌ๋ฆฝํธ engine compares. So, IE 9's new script engine, you may have heard of it by its internal code name, Chakra, is faster than many browsers. One thing to keep in mind is that we've done very little SunSpider-specific work at this time. We will continue to improve IE 9 script performance. ย It's interesting to note that the gap between IE 9 and some of the other browsers to its right is about an eye blink, it's about 300 milliseconds, and it took 70 seconds to identify the 300-millisecond difference.
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Letโs put this all together using the Flying Images demo that we just saw. In Internet Explorer 8, we spend about 0.13 seconds interpreting the ์๋ฐ์คํฌ๋ฆฝํธ โ thatโs the green on the chart. The purple represents almost ยผ of a second writing to the DOM. Finally, it takes us almost a tenth of a second to draw the image on the screen. All told, weโre at just under half a second to move one animation, and the CPU is at nearly 100% the entire time.Letโs take a look at how Internet Explorer 9 handles a single animation. [CLICK]. Each iteration takes only a fraction of a faction of a second, and the CPU, hardly has to move.
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Weโre not only working hard to make our code faster, but to provide you with tools so that you can make your code run faster. Internet Explorer 9 introduces a new set of ์๋ฐ์คํฌ๋ฆฝํธ profiling APIโs and metrics that can help you instrument you code, so you can better understand where the browser is spending most of itโs time. In addition to using these APIs when developing your site, you can use them to better understand how long it takes for a users page to load, and send those values back to your server in real time.In the code example on screen, Iโm using timing.navigationStart, which returns the number of seconds past January 1, 1970 (UTC). By using the Date() function, I can convert that to a local date/time value. To get the end time, Iโd use the timing.loadEnd. To get my entire page load time, I can use timingMeasurements.navigation or calculate the value myself. Weโre working closely with the W3C Web Working Group to get these new APIs standardized and moved from a draft to a specification that can be implemented across all browsers. When the draft is approved, there will be only one window.performance interface that will work across all browsers, using the same mark-up.
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Developers want to use the same HTML, the same script, and the same markup across browsers. That's the goal of standards and interoperability. No need for different code paths for different browsers, and that's a key goal for HTML5. We love HTML5 so much, we want it to actually work. In IE 9, it will. We want the same HTML, the same script, the same markup to just work across browsers. And so in IE 9, we will do for the rest of the Web platform what we did for CSS 2.1 in IE 8.
Itโs not enough to just make sure weโre implementing the features and specification that you want. Weโre working directly with the W3C to make sure that the specifications that are written are clear and strong. That we can figure out the ambiguities early, before implementation and that everyone has a voice at the table. The Internet Explorer engineering team is well integrated into many different working groups on the W3C, including the HTML5 working group (where Paul Cotton, a Microsoft employee is a co-chair), the SVG Working Group, and many more.Just to give you an idea of who is involved in a working group, Iโve got a few stats from the HTML Working Group. There are over 40 W3C member organizations, more than 400 participants, 280 invited experts, 9 mailing lists. Itโs a big, but very important group!Working with the W3C also includes working on testing task forces so that there is an interoperable test suite that all browser vendors can agree upon.
When we were building Internet Explorer 8, we spent a lot of time making sure our CSS 2.1 implementation was rock solid. While doing that, we realized that there were less than 100 tests in the W3C CSS 2.1 test suite, no where near enough to validate a spec like CSS2.1. Because of that, we worked with the W3C to donate over 7200 CSS test cases, to their test suite.We think itโs vital to have a true, interoperable test suite that all browser vendors can agree upon as a method to test their implementations of HTML5 and other important web standards. Thatโs why as weโve been building Internet Explorer 9, weโre doing the same thing for the rest of the platform what we did for CSS2.1 in the Internet Explorer 8 timeframe. Weโve donated over 100 test cases to the W3C to date and there are many more to come! You can see the tests weโve donated so far on the IE Test Center linked off the IETestDrive.com site.
When we talk about โsame mark-upโ, we really mean one major thing. We want the mark up your write, to work the same way, and the right way in every browser. The example you see on the screen shows Internet Explorer 9 Platform Preview compared to Chrome 4. Both have a dashed border, as well as a rounded corners via the CSS3 border-radius property. In Internet Explorer 9, the dashes are the same width all the way around the border, and equal spacing between them. Chromeโs dashes seem a little random. In Firefox 3.6, this works a little better, except in the corners, there are no dashes โ itโs just solid line.The same mark up means the code you write works the same way, and the right way, in every browser!
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
There are some important additions and updates that we needed to make to the DOM in order to enable same mark-up for developers. Internet Explorer 9 now has full DOM Level 2 and DOM Level 3 Event support. No longer do you need to special case for Internet Explorer 9. Weโve also added new support for DOM Range an important part of the HTML5 Text Selection APIs that provide a simple, consistent way to extract a piece of a document.DOM Style and DOM Traversal also make it easier to use the same mark-up without having to special case!
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
HTML5 applications will push the limits of graphical richness and interactivity. IE 9 will run HTML5 applications better by taking advantage of PC hardware through Windows. We call this GPU-powered HTML. HTML5โs graphical richness demands a high-performance graphics subsystem. By harnessing the power of the GPU, we can achieve complex visual effects like alpha-channel blending, smooth, high-definition videos, and lower CPU load.
Many people think of hard-core gaming machines when people say โGPUโ
But thatโs not the case. For the last 8 years, every Windows machine has shipped with a GPU. Whether itโs a super-powerful gaming rig, or a small compact netbook, thereโs a GPU in there.
In fact, based on our research, the GPUs in todayโs computers are pretty good as well. Through the Customer Experience Improvement Program where customers have the opportunity to opt-in and send anonymous data about their computers, we know that almost all of the GPUโs out there score at lease a 4!
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9
Show Spinning Images demo in IE8Show Spinning Images demo in ChromeShow Spinning Images demo in FirefoxAdd additional imagesZoom InShow Spinning Images demo in Internet Explorer 9