Episode 11 of The SitePoint Podcast is now available! This week your hosts are Patrick O’Keefe (@ifroggy), Stephan Segraves (@ssegraves), Brad Williams (@williamsba), and Kevin Yank (@sentience). They are joined by Microsoft’s Platform Architect for Internet Explorer, Chris Wilson (@cwilso).
Listen in your Browser
Play this episode directly in your browser! Just click the orange “play” button below:
Download this Episode
You can also download this episode as a standalone MP3 file. Here’s the link:
Subscribe to the Podcast
The SitePoint Podcast is on iTunes! Add the SitePoint Podcast to your iTunes player. Or, if you don’t use iTunes, you can subscribe to the feed directly.
Thanks to all the members of the SitePoint Forums community who submitted their questions for Chris!
Here are the questions we put to Chris in this episode:
- What does the Platform Architect for IE do?
- Why did IE8’s default rendering mode change?
- What’s the deal with the Compatibility View button in IE8?
- Is it true that users are able to remove IE8 from Windows 7?
- If not IE, which browser would be your favorite?
- What’s the plan to get IE6 users upgraded?
- How long will each of the rendering modes in IE be preserved?
- What has been the most drastic change to how we use the Internet since IE6?
- Are there any plans to allow multiple versions of IE installed side-by-side?
- How does the Internet Explorer Developer Toolbar compare to Firebug?
- What’s the size and shape of the Internet Explorer team?
- What’s the real value of “paving the cowpaths” in HTML5?
- What big changes in HTML5 promise to be most exciting?
- Does HTML5 threaten to be a monolithic spec? Should it be split?
- What steps are involved in getting new CSS features added to IE?
- What is IE’s plan to compete against the rising popularity of alternatives?
- The font debate: Why is loading TTFs dynamically not enough?
- Which instrument did you play in your rock band?
- The web stack isn’t suitable for building applications. What’s the fix?
Thanks for listening! Feel free to let us know how we’re doing, or to continue the discussion, using the comments field below.