To take an example close to my heart, IndexedDB was proposed more than 5 years ago and has been available in IE, Firefox, and Chrome since 2012. ( Correction: actually, they have.) When you start browsing, the list goes on and on.Įven when Apple does implement newer APIs, they often do it halfheartedly. All of the APIs I mentioned above are not implemented in Safari, and Apple has shown no public interest in them. I think there is a general feeling among web developers that Safari is lagging behind the other browsers, but when you go to a conference like EdgeConf, it really strikes you just how wide the gap is. I heard them referred to cagily as “a company in California” or “a certain fruit company.” Their glowing logo illuminated nearly every laptop in the room, and yet it seemed like nobody dared speak their name. There was one company not in attendance, though, and they served as the proverbial elephant in the room that no one wanted to discuss. So we had lots of fun peppering them with questions about when they might release such-and-such API. The average Twitter follower count in any given room was probably in the thousands, and all the major browser vendors were represented – Google, Mozilla, Microsoft, Opera. It featured panel talks and breakout sessions with a focus on technologies that are just now starting to emerge in browsers, so there was a lot of lively discussion around Service Worker, Web Components, Shadow DOM, Web Manifests, and more.ĮdgeConf’s hundred-odd attendees were truly the heavy hitters of the web community. Last weekend I attended EdgeConf, a conference populated by many of the leading lights in the web industry. I leave it up as a historically interesting artifact. Update: This post represents my views before I joined the Microsoft Edge team, and before I got involved with browsers or web standards in general.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |