|« April 2014|
Yesterday, reports surfaced that Internet Explorer had suffered a dramatic drop in "market" share against Firefox, Safari, and Opera. Reports of IE's demise, however, were quickly shown to be exaggerated. True, certain sites reported double-digit drops in the percent of their visitors using IE—but they were sites with highly technical audiences, the kind you would expect to be atypical early adopters. According to this article, IE's drop among more mainstream users is much more modest: down from 95.5% to 93.7% (not quite three percentage points) since June.
But wait: there's more to it than that. Sure, Firefox isn't dominant, and has a long way to go before it is. It's quite likely that it will never completely overtake IE. But that's not really the point. The point is that, all of a sudden, modern browsers (especially Firefox, but also Safari and Opera) can no longer be ignored by organizations developing web apps.
Let's look at the events that have brought us this far.
Firefox overtook IE in the feature department a number of months ago, but it was still a little rough around the edges, and the version numbers (below 0.8) reflected that. But then, just under three months ago (following a rash of new security bugs in IE and some worms that took advantage of those bugs) the U.S. Department of Homeland Security issued a recommendation that Windows users consider switching. It was a gentle recommendation that lacked teeth or urgency, but Firefox downloads went up immediately, and have continued at a higher rate than before.
93.7% still seems like a really daunting market share for IE. But turn it around: that's more than one out of every 20 web users (also known as "potential customers" to commercial websites). Just three months ago it was slightly less than one in 20; today it's trending toward 1 in 10. That's significant.
Many companies write web applications that support only IE. Although I've never agreed with that strategy, I can see how some are convinced that it's a reasonable one. But I suspect the problems with an IE-only approach will quickly become clearer.
The extent of IE's dominance today is not the point. The point is how quickly other browsers can become too significant to ignore. It's fairly easy for some to justify ignoring 5% of users. But can you afford to ignore 10%? If current trends continue, modern, non-IE browsers will have a 10% share by the end of the year. Their share will have doubled in six months.
And there are good reasons to think the trends will continue. Firefox' lead in features continues to grow, and it's becoming quite polished. The 1.0 release will appear soon, and that's bound to bring increased publicity, interest, and acceptance. IE's security woes have calmed a bit, but I don't know anyone who believes they're over for good. Meanwhile, Firefox has very few security flaws, and they tend to be fixed very quickly.
These thoughts began swirling in my head this morning, but that's not the end of it. A little while ago I decided to download the Firefox 1.0PR release for my wife (she's been using Firefox, and before that Mozilla, for a long time—and no, not because I told her to). When I saw the front page of mozilla.org it felt like the first rumbling of an avalanche. Today, in his column in the Wall Street Journal, Walt Mossberg wrote this:
I suggest dumping Microsoft's Internet Explorer Web browser, which has a history of security breaches. I recommend instead Mozilla Firefox, which is free at www.mozilla.org. It's not only more secure but also more modern and advanced, with tabbed browsing, which allows multiple pages to be open on one screen, and a better pop-up ad blocker than the belated one Microsoft recently added to IE.That's big. I repeat: what matters isn't IE's share today; it's how quickly things can change. When Walt Mossberg, Homeland Security, Fortune magazine, and the German government (among many others) are all saying "dump IE"—and the signs are that many people are switching to Firefox even prior to the 1.0 release—do you really doubt that IE could suffer major losses over the next year or so? Yes, they might be able to hold off this threat, but if you're writing web apps today, do you want to bet on that? Do you want to risk having to explain why you're turning away 15% of your potential user base?
(Oh, and one more thing. "Dump IE" is actually the sixth recommendation in Mossberg's column, one of several things he suggests doing if for some reason you can't follow his first recommendation. That first recommendation, which makes all the others unnecessary, is "chuck Windows altogether and buy an Apple Macintosh." But that's another blog.)
For several months now, my friend Stuart Halloway has been talking to me about his new job, and the project he’s been working on. I noticed a couple of weeks ago that the website is finally showing some details—the company is out of stealth mode, and I can finally start talking about it.
Stuart’s job is with a company called Near-Time, and the product is called Flow. It is, quite frankly, the collaboration tool I’ve wanted for a long time. I saw an early version in October, and even in a rough state it was breathtaking. Flow includes the best of Wikis, blogs, browsers, bookmark managers, outliners, and email clients, all in one program. Flow gains a lot of power from having all of those things integrated into one interface (and it doesn’t hurt that it’s a good interface).
Although Flow is useful for individuals, it’s designed for collaboration. It seems to me to be an ideal tool for collaborative research, planning, and development work of various kinds, especially (but not only) if you can’t be face-to-face. Best of all, Flow is a collaboration tool that doesn’t require constant connectivity. The assumption of intermittent connectivity is baked into Flow and the protocols it uses for information sharing.
Near-Time is preparing for an early-access release of Flow in the coming weeks. If you and some others in your group use Macs, I urge you to register and try it out. I think you’ll be impressed.
Update: Matt Brubeck (any relation to the Brubeck from the image above?) forwarded an explanation from John Gruber of Daring Fireball fame:
In short, iTunes 4 uses 9-point text for these lists, and Mr. Vanderburg has changed the default settings for anti-aliasing in the General panel of System Prefs such that 9-point text is not anti-aliased. Thus, what he is seeing is what he asked for.
I don't remember asking for that, but I suppose I did. And with the new release, iTunes changed from 10-point to 9-point. But what really made the ugliness obvious was the occasional antialiased line, like the Béla Fleck CD above. What's going on there? John continues:
However, Jaguar introduced a change in text rendering such that Unicode text strings are always anti-aliased, in every application, no matter what your pref settings are. That's why text with accented characters is anti-aliased, but plain ASCII is not.
Thanks Matt, and John. Preferences setting changed; all better now. :-)
Update 2: Yes, Matt Brubeck is a distant cousin of the famous Dave. What a delightful coincidence! I blog a weird problem, just happening to use a Dave Brubeck CD in the screenshot. And one of my blog readers (there aren't that many!) -- who happens to have the wherewithal to find out the answer to the problem -- is a relative.
As Duncan says: I love blogspace!
It still annoys me. But I am used to it. I know I'm used to it because Chimera doesn't have that behavior, and it really throws me. Click ... click ... click click ... drag ... oh yeah, gotta remember, it's easier if I use Command-L.
I'm glad the Chimera folks have decided to stick to UI conventions. (Of course, Chimera's in beta, so perhaps they just haven't added that “feature” yet.) It's not as though the right way is really difficult. There are three easy ways to select the whole URL field: drag across it, triple-click, or Command-L. But it's annoying that I've had several years of training in the wrong way.