Thinking » Tags » IE8
Author’s Note: This is the first post in what we hope to make series: “Ask a Web Strategist”. These are intended to be relatively short, public answers to questions web technology and strategy we receive. Do you have a question? E-mail us!
Question: I’m all bent out of shape about the Flash vs. HTML 5 debate. I’m interested to hear your opinion about it. Will Adobe Flash still have a place on the web in 5 years?
Answer: Generally, trying to predict where any technology in a field susceptible to rapid change will be in 5 years is a losing game. Flash will probably be around for many years to come, but we’d bet on a much smaller place.
Internet Explorer 8 is out, and a lot of people – technically sophisticated and otherwise – are wondering what, if anything, this means for the web. As professional web developers, our view is that while Internet Explorer 8 is an incremental improvement over its predecessor, we’re mostly disappointed by its lack of progress.
Having read a variety of takes on IE8, we were inspired to write this article for two audiences. First, there’s little in the way of concrete examples and clear explanations for a large swatch of the business technology decision makers (that many of our clients represent) who are often savvy about technology, but look to organizations like us for a deeper understanding of the strategic, cost, and technical significance. Second, reading the comments on tech savvy websites like Neowin, Digg, and the Winsupersite have me concerned that there’s a growing and false notion that IE8 is just great, and its rendering problems are the result of web developers writing non-standard code optimized for IE7.
To understand why IE8 is a legitimate disappointment, we need to start by providing background on how different browsers impact web development, both from a cost and design standpoint. If you think you already have a handle on this, you can skip ahead to our 3 straightforward examples of IE8 disappointments.