 Okay. Microsoft Internet Explorer. Iya. It's not on. It's on. Okay. Oh, okay. Okay, hi. My name is Riza. So, in here I just want to share with you regarding the Microsoft Edge. Actually, I don't know much about it, only that it's already released and is tested, and then this one is just to we want to, we want to, from Microsoft side we want to share as much as we can regarding the Microsoft Edge, which is the Edge HTML rendering engine. And this is because some of us as a developer, web developer, for example, think that this is maybe some sort of IE, mix of IE, that kind of thing. So, let me try to explain everything and this is from Microsoft. I usually in my meet up, I become myself, so this time I have to choose my wording. Okay. Okay. So, the title is Meet the Edge HTML. Number one, there is no new HTML. It's just the name of the engine, Edge HTML. Number one, because there is a question is asking what Microsoft creating another HTML. No, it's enough. Enough is enough. No more. Okay. It's no more. So, maybe you remember this. Yes. And the more painful side is this one. You can see the age of Trident is the same like the age of JavaScript is 20 years. So, from Internet Explorer 1 up to Internet Explorer 11 we're using the same engine. Okay. Believe it or not, the legacy one from one to, they are never changed. It only adds something new. For example, this one, remember this, the duck type quirks, strict in the Trident. Anyone use IE5 before? You remember how pain use okay, that's good. That time, yes, because, yeah. And then IE6, yes, the beginning disaster for me. This is starting become it's like a no way round. But, well, that time maybe there's no choice. And then we jump around to IE8. But you can see that this document mode, IE has document mode. So, instead of updating the engine Microsoft add lots of new document mode. And IE8, you can see the HTML4, ES3, CSS2, and then CSS2.1, nothing happen, you can see just add the UA compatible user agent. And then IE9, same IE10, getting worse IE11 worse for the legacy but good for the new HTML5 because it's already moving to the the modern web. Anyway I feel like this. Seriously, that's what I feel. Everything that we create, for example, I create the web, everything running JavaScript, everything tested in Chrome, it's working fine, testing in Java, it's working fine. And then the HTML oh, see, even I do that in Taipu. Sorry about that. HTML is our new web rendering engine. Let me just edit that because seriously, I just do it. I just add this pitch just now. So, the idea is like this. I should just work for everyone. For users, developers and businesses. So, Microsoft think a lot of the painful time for the browser. I think it's May 2014 and decided enough. That's it. No more IE. Something like that. So, that time is decided to create something new. And the idea is the web should just work. Simple, for everyone. So, don't care whether you're coding for anything once you run it, sorry, once you open in Edge it's supposed to work exactly like what you want. That's the idea. It's not easy. So, remember this? Interoperability means the web just work. You remember this? IE hate? Who knows that from where? It's in the very famous social networking site. They have this JavaScript, for example. Well, in Chrome the error does not occur. The XML is appended successfully for some reason IE seems to be calculating wrong. And no matter how KO object, child window got lost, horrible behavior in IE, why does the following code unspecified error, it happens in IE. But for some reason the guy who developed this code he joined the web summit 2015 I think is on May as well. So, he admitted that some of the specification of IE is correct, actually. It should return an error. So, he tested the Chrome, Safari and Firefox make a consensus. Don't generate the error. So, for some reason IE also say okay, let's remove that. It's not become an error. So, it's become a standard. And a lot of JavaScript to work around that kind of thing. And I'm just going to go through this is one of one reason. The other reason is this. You see in Firefox is rending like that in Safari is rending like that and IE, look at that. Yeah. It happens to my web, I create a website for e-commerce for book e-commerce in Indonesia. It happens like this as well. What the hell? What is going on? So, what they did is enough and then Microsoft create this rendering engine of work from the past. So, they get the old IE 11, they split everything throw the shit out. Seriously, they throw the shit out. And then it's about 220,000 lines of code, real code is not space real code. It's 300 API remove. Okay. And Microsoft create the new 300,000 added new line which is 49 new major features. It was a fork from the past. Yeah. So, is a learning curve for Microsoft that the browser you cannot extend instead you just have to recreate maybe it's the only company now that learns that lesson very well. I hope Apple Safari also learn that lesson. Yeah. Yes. Yes, exactly. How many years? Never change. Yeah. They just keep adding, adding, adding, adding. Okay. So, Microsoft edge is interoperable. Sorry. And I just want a little bit to give some highlight about the old one. Yeah, this one. Just go through. So, this is different. The edge HTML is the default engine interprobability and for more than HTML website. And this one is compatible. This is the document mode. Microsoft have reason to keep this document mode. Because a lot of application running is using IE. Like us, if there's new browser new engine, we tend to try, isn't it? But for company enterprise believe it or not, some of them still using IE6. But that's why Microsoft cannot remove the document modes. Okay. But in Microsoft edge it's gone. No more. So, for the legacy apps, Microsoft rely on the old IE 11, which is still available in Windows 10. That's the last thing you can use for the old document mode. But the new web browser is modern web. Totally modern web. And I think you know this one. Yes, the lies. You know the pack of lies. You know that, eh? Look at this. Mozilla 5.0. Netscape 6. 1997. Serius? But I also add in here but some of the web developer they do UA sniffing. That's the problem. So this sniff if Chrome do like this, if Mozilla do like this, if Edge do like this, or if IE do like this. So, instead of creating the good HTML5 and JavaScript, they break the HTML. Okay? So it's not doing the proper HTML5, instead they just break. It's because of this. Okay? And I think remember this. Anyone using this? I do. What is this? Yes. Just to check just to check whether it is mobile. We haven't add Windows Mobile phone. So every time there's new mobile product it will add in here and this one it's become a mess now. Okay? It's become a problem. So this one Microsoft learn everything by doing all the research for 5 years I think. I remember it's 5 years before saying that enough. Okay? So it's not like just yesterday. It's already like a long time. So currently to date 4000 plus bugs is removed from the main engine. Okay? And it's become the new HTML. It's not using IE engine, no? No more. No more Trident. Trident. So it's the real new engine create from zero and removing this kind of bugs. So Microsoft found this bug is because for example a lot of Chromium or a lot of JavaScript doing this. A lot of HTML doing that. So they finally found this is the web that people use now. So that one that the thing is not there remove. Okay? For example like this one. It happens like this 8.1 and then as edge support for webkit transition it shows the correct website. Okay? Also this one Windows Phone 8.1 You see that? By adding the new user agent it works. So this is Microsoft doing the research at the back. And then where is it? It's constrain and down the phone. Other phones and this phone is showing. So the learning is like that. So this is why the web developer did actually. So it follows that rule. Also this one for example you see it's supposed to be a gradient in here. But it's not showing. Not only in IE Firefox also is not showing correctly. But and then with adding some code webkit gradient it works. This one as well. You see this wipe doesn't work and it becomes good. So here's the map. Here's the Internet Explorer Firefox, Chrome, Safari this is the mobile website this is the desktop what Microsoft did is remove this the entire chunk. Done. And then adopt this. This is the web that actually running in the world now. So the interoperability features available 4200 plus fixes this all thing has been fixed in Microsoft Edge. Some of them is still not finished because it's still undergoing development but you can check the status is in here. Dev.modern.ie then you can see everything it's under development. How about JavaScript? You know that Edge is using EScript, ECMAScript 2015. I did test that it cannot run in Chrome cannot run in Safari but it run in Edge It does not mean that they're not going to do it. Chrome will be update, don't worry about that. The thing is Microsoft now don't want to there's no more racing but let the people that create a web and the people that use the web can be happy. That's the idea now, yes seriously. So they don't, Microsoft don't care about the speed you're not going to racing about this, don't care. You cannot run in here perfectly but you can run in Edge for example, done. That's what Microsoft idea. So even someone doing this Octane is worth. Google Google or the testing for so this is the speed this is not from Microsoft I think it's from Google and this one is from and the Edge is Evergreen there will be no more new Windows and then new IE no or new Edge no the Edge and the Windows has a different updating. The good thing is Edge now the update is not from Microsoft, it's from us we give the feedback Microsoft will do that. The same like the Windows now the Windows 10 that you see is from 5 million people that give the idea and Microsoft read one by one group it and follow it including the Edge now, I'll show you the link at the end if you don't like it you say it, it's only 3x Edge changing because some developer don't like it Microsoft change it again, you like it until everyone agrees, okay this is the one something like that seriously, it's us now who control Edge if you don't believe me, you put something something that you really want and a lot of people in the world support that Microsoft will edit that feature, okay so you can go to this Dev.Moderno.IE read everything about that and the current release the one that I use this Windows 10 10166 build 10166 already can do for web development so you can start download and you can use it as if you want to test Edge including the F12 tools as usual everything you see that ugly ya it'll be no more done so the idea is now to tell the web developer to use proper HTML5 follow the rule follow the rule of HTML5 and everything will run smooth but if you don't follow, you follow something else, it's okay Microsoft Edge will capture that, will put as one of the fix internally so until now trillions of data being crawl to website still crawling finding telemetry is like crazy until this is the problem until meet no more different even 3% slightly for the javascript javascript speed Microsoft very concerned already 99% nearly fastest okay the page is like this and you see there is a feedback ya there will be a feedback there you can send a feedback and you can boot you can boot inside you just click anything in here for example like this one you boot and ya the more you boot, you will get it or you can do like this, user voice this is an example Microsoft edit to edge okay so the web developer and the people that use the browser will be happy with that so no more, this is Microsoft's technology, this is no it's our technology we're the one who control that huh? they should have console set yes I saw one of the video from the if why Microsoft don't use the current engine what is the chrome engine why don't use that why don't use bling Microsoft just respond like this it's better have diverse engine but as long as it's always up to date it's better like that and Microsoft will not add features instead of fixing making new so it's not like just adding this without thinking about this should be good la for web developer so I need your help because you're an expert I know your influencers in javascript HTML I need your help so for example like this one do not use UA sniffing don't detect edge no need I'm not saying it's okay you want to do that some of the website I saw in Singapore is already detecting if IE equals to edge there's no edge will not just go there's no compatibility there's no active edge so UA compatibility is gone for example I cannot give you all this because a lot of specification you just go to modern IE there's a lot of new spec it is gone I think it's 600 in IE no more for example it's okay edge will just go but I mean what for as a web developer you know that edge will not read that why we put UA sniffing if you take away the ability to sniff then there's nothing to sniff just what the two say if your UA is exactly the same even from here on then there's no way you can even detect edge in the first place there's no problem as long as you're doing the right HTML but the browser if it doesn't identify itself the edge prevents the the code is from identifying avoid UA sniffing as much as possible I know we should but if you don't identify yourself as edge they can't sniff you in the UA string they have edge 12.0 what don't you just like Microsoft just say I'm negatory nobody can sniff you cannot because the UA string is part of the web development you cannot remove that but it does not mean if you're using edge are you going to sniff for Mozilla for example that's what I mean so why you sniff for edge because there's no UA compatibility UA compatible in the HTML so people think that if edge is like they treat edge like IE just treat it like normal HTML5 that's the the message no need to treat edge like IE no need to put if edge do this you just treat edge like the normal HTML5 browser and it will work what you're actually using user agent sniffing yeah this is one of the example actually the other one is for example do use feature detection for example feature detection is better to use feature detection because sometimes they put in the CSS in the JavaScript they use this one and then they use one for Chrome one for Mozilla which is not the correct way so it's better to use I use modernizer make it easy just put modernizer done because it's an industrial standard and it's used by enterprise put it done something like that so there's one feature that does the same thing the second one has 8 times the votes because the second one is already supported by 3 other browsers obviously we're talking about WebRTC and Microsoft deciding to go for more RTC instead of what everybody else does and what gets the most votes you can find out some more information for me you can ask Chris later because Chris is the one he's the R&D guy I don't know the answer for that because 3,000 votes here currently not planned and then the other one is like 600 votes in development yeah it's something like previously in IE Microsoft for example only 9,000 websites in the world believe it or not even I was shocked so to get the new engine for example new IE Microsoft crawl only 9,000 websites and it becomes the pattern example of the new update but now it's trillions of pages scrolling and then finding okay don't worry about that and if you think this one need to be what do you call it furnish or something like that you just send a feedback you go to dev.modern.ie send a feedback and for the tough question which is I don't know the R&D guy you can talk with I did get that kind of thing but some of them I still cannot say anything because it's under development now right if user agent contains edge then write most fucked up website maybe okay so that's the idea because this one is the most issue on the web that Microsoft it's not only for IE or for edge even for Chrome for Safari it works in Firefox it does not work in Safari because of this it does not work well in Chrome or it works well in Chrome does not work well in Safari is because of this as well that's why Microsoft send a message tell the web it's okay and the reason that the sniffing hasn't been removed the reason we still have the identified agents is because bugs go out there and they versioned yeah yeah the easiest way is just for you is just to if you think it's like that why don't you open it in edge see whether it's is it running normally or not actually I challenge you anything that you think is not working in IE run it in edge for example go ahead for example send me an email seriusly I will send to the guy and they will fix it because again it's not about the browser itself but it's about the web people using the web in the world and the developer also so if I will use I just give you a suggestion I support this it's not about Microsoft because of headache headache if it's too many standard like too many for example like too many standard I cannot tell you the numbers but too many standard you don't notice in the real world some of them create their own standard for the web so each web in the world not talking Singaporean but is a lot providing information which is I never seen before seriusly in the world is like this so there is no standard web actually in the world there is no standard cannot find one standard even though W3C I saw it is like they use for example you can see the documentation even they say standard but Microsoft create edge just to just work the idea is just just make it work whatever you do just make it even you want to target Chrome go ahead run it in edge it will run work normally just like that if you just want to target one browser mobile browser for example target safari go ahead you just create if you want to test you just create only specific only for safari run it in edge it will run normally something like that so that's for me maybe tough question please don't ask me because seriusly I support the JS conference Microsoft support it yes hopefully hopefully Chris Chris will be there you can ask tough question regarding this because he's the one he's the boss seriusly oh ok sorry about that spoiler alert ok, any question so I need your help because I also do web developing we just do that we just use the proper HTML proper javascript it will work fine no need to do this to do that for edge it will just work even if you want target IE11 you just create only for IE11 you think it will not work in Chrome but it will work in edge or you just target only for one browser it will just run in edge ok if you can get edge to run yeah, a lot of people asking that so maybe small demo yeah, hear this ok seriusly it is like you is there a sound in here? nope just wanna really at an inflection point for the web looking back a major new browser only comes out every 5-10 years and for Microsoft, we've only had one and it's been around for 20 years we realized that it was very very hard for us to make an engine that would stretch across 20 years of content and internets and on the open web so that's why we decided to split the engine and have an older engine for content made only for IE and a newer engine that we can always keep up a date and IE has been the browser used through the decades by millions of people around the world and with the new rendering engine that lets us sort of clean shop let's just get rid of the old things that were from the past that might have haunted web developers today so the first thing I think that hits you when you come to work on a web browser is the scale of the problem you learned that the web is 44 billion websites and then you start to think okay, I can't cover 44 billion websites so we need to start to prioritize in the past, the internet explorer team always tested against the top 10,000 sites or top 9,000 sites we had a metric that we used to basically say that we are as compatible or more compatible than we were in the previous release it turns out that's not enough it turns out that the tale of the web matters the rest of the web is gigantic and people go to very very different sites so we got a lot of bug reports from people close to Microsoft and people all over the world where their local school website wouldn't work or their barbershop website wouldn't work and these are sites that would never be in the top 9,000 so just focusing on the top 9,000 it doesn't give you a browser that works for everybody all the time so what we decided to do instead was use the crawler to detect patterns that exist in the tale of the web and in the head of the web we crawl millions of URLs every night and the Bing crawler itself crawls trillions of URLs monthly so in the tale of the web we fix patterns instead of sites and by fixing patterns sites just end up working so even though we're never going to be done with compatibility problems I think what we've done in this release with the engine split bringing up the new rendering engine is we've really laid a foundation and a set of best practices and engineering processes on the team that's going to really allow us to evolve more quickly and react in a much more agile way mixed out for our users and developers in a more timely manner we're not abandoning standards in the past we had a very spec purity approach and that really isn't the best way to do it you have to be a little bit more pragmatic when you build a web browser but you also have to work with other browser vendors and W3C to ensure the specs accurately effect what old browsers do and what developers want to do Project Spartan Journey has been about sharing our plan what we're building, why we're building it build next, earlier than ever before we launched our platform roadmap which developers can know what standards we're looking at we launched User Voice where they can provide ideas and vote on what should be next we are active in Stack Overflow on GitHub and on Twitter seeking feedback daily this is very much a community process and we want to take the feedback from developers and users to help shape the product well before it ever ships screen is really about acknowledging that the web is this constantly evolving thing you need a web browser that also moves at the speed of the web and with Windows 10 as a service we're going to be able to evolve Project Spartan at the speed of the web in the 5 years that I've worked on the browser at Microsoft I've not seen as much innovation and dedication to the products as in this release we fixed over 3000 issues limited over 45 different new standards the pace of development here is impressive I'm really proud of that and I can't wait to see where we go next for me, thank you very much I hope you like it