Revision 211: Project Spartan with Jacob Rossi

Published: March 8, 2015, 7 a.m.

Herr Rossi hat das Gl\xfcck gefunden. In einem Spartaner. Jacob, seines Zeichens\nProject Manager bei Microsoft f\xfcr den IE Nachfolger, erz\xe4hlt ausf\xfchrlich alles,\nwas wir vom Projekt wissen wollten und uns nicht fragen trauten. Ab nun in\nEnglisch:\n\n\nSHOWNOTES\n\n[00:02:08] PROJECT SPARTAN\n\nJacob gives deep insights behind the strategy of Spartan, how it\u2019s related to\nthe Internet Explorer of old, and what we as web developers can expect from it.\nIncluded are: The difference between EdgeHTML and Trident, Enterprise Mode (not\nrelated to Leonard Nimoy) and overall performance discussion.\n\n[00:44:49] WEBRTC AND ORTC\n\nMicrosoft\u2019s browser was still lacking a WebRTC implementation. This will change\nwith Spartan, and more: We also will get the next level called \u201eObject RTC\u201c.\nJacob explains what\u2019s behind.\n\n[00:47:45] POINTER EVENTS VS TOUCH EVENTS\n\nJacob not only is deeply involved in Project Spartan, but has also co-written\nthe sublime and solid Pointer Events API. He explains how it came to fruition,\nand how Microsoft will behave with not having Apple on board. While the Working\nDraft crew is strongly ranting about Apple\u2019s broken Touch API, Jacob calls\nSafari developers \u201enice guys\u201c and tells how it came to reverse engineering the\nstandard by the W3C and the implementation in Windows Phone.\n\n[01:00:09] VENDOR PREFIXES AND WHAT COULD BE THEIR SUCCESSOR?\n\nThis also leads us to a discussion on vendor prefixes, which we all think are\nbad and should be avoided. Nevertheless, browser vendors need to test things.\nJacob gives ideas. Nothing written in stone, tough