Category: Browsers

Browser Wars: StatCounter Data for Europe

2009-04-17 / spierzchala / 0 Comments

In the previous installment in this series, I looked at the browser share in North America. Across the water in Europe, the browser distribution metrics show the unique flavor that this continent brings to this fluid arena.

In Europe, MSIE7 and Firefox 3 are effectively tied for the lead as the most dominant browser, followed distantly by MSIE6. As in North America, MSIE8 has substantially increased it’s market share since its March 19 2009 release, but it has not caught up to Europe’s favorite son, Opera 9.6.

What is clear is that MSIE8’s gain is MSIE7’s loss. Comparing March 1-19 with April 1-19, the shift away from MSIE7 is almost equal to the shift to MSIE8, meaning that people that are upgrading to MSIE8 in Europe are doing so, in the most part, directly from MSIE7.

There is little or no change to the MSIE6 install base, indicating that this is an entrenched population, likely in large corporations or government agencies.

Like in North America, the big factor to watch is how quickly the MSIE6 population decreases. Europe already has an entrenched population of alternative browser users, mostly with Firefox 3. When Opera 10 and Firefox 3.1 are released, it is likely that these people will move directly to these browsers.

What remains to be seen is how the strong anti-Microsoft sentiment in Europe affects the adoption of MSIE8.

StatCounter Browser Stats – March 1-24 2009

2009-03-24 / spierzchala / 3 Comments

Using the visitor trending data collected and shared by StatCounter, I have undertaken a general analysis of browser distribution by global region. These metrics are collected using the embedded tags that StatCounter customers embed on their site to collect visitor metrics for their own use.

US data shows that MSIE 7.0 is in a dominant position, with Firefox 3.0 in the 25% range of market share. This trend extends into the North American data, which is heavily influenced by the US trend.

MSIE 8.0, still reports a lower distribution than Firefox 2.0. This data is most likely based on the usage of MSIE 8.0 RC1 version, as MSIE 8.0 was only released in GA last week. It is highly probable that these stats will change in the very near future with the release of MSIE 8.0 to Windows Update.

In the EU, where fear and loathing of Microsoft runs deep and true, Firefox 3.0 is approaching parity with MSIE 7.0. Also, the perennially favoured native son Opera makes a very strong showing with their 9.6 release.

Asia is a Web designers nightmare, with MSIE 6.0 continuing to be the most reported browser. This is concerning, not simply for design reasons, but for web compliance reasons. Effectively Asia has throttled Web development to an old warhorse, but to such a degree that there must be some overriding advantage to using this browser.

As an example, the statistical comparison of four Asia nations is broken out below. We’ll start with Japan where MSIE 7.0 has a clear lead in the statistics.

However, when China (People’s Republic), India, and South Korea are added into the analysis, the pull towards MSIE 6.0 is massive.

This trend needs to be studied in greater detail in order to understand why MSIE 6.0 is so popular. Is it because of licensing? Continued use of Windows 2000? Compromised computers? The data doesn’t provide any clear or compelling reason for this trend.

Moving to Oceania shows a return to the trend of MSIE 7.0 being the predominant browser with Firefox in second place, with these two browsers showing a substantial lead over the remaining field.

South America sees MSIE 7.0 as having the largest market share, followed by MSIE 6.0 and Firefox 3.0. Effectively there are no other browsers with substantial market share at present.

These statistics show that the three most dominant browser platforms by market share are the two MSIE platforms followed by Firefox 3.0. This is likely to change with the MSIE 8.0 GA last week and its predicted release to the masses via Windows Update in the near future.

However, the release of MSIE 8.0 may not be as exponential as is predicted. Corporate IT policies, which have been slow to embrace MSIE 7.0, are likely not going to make a giant leap to MSIE 8.0 overnight. Adoption among the general population will also depend on the ability of existing Web applications to adapt to a more standards-compliant browser platform.

Noticeably absent from most of these statistics is Safari in a position to challenge the three leading browsers. This indicates that even hardcore Mac users continue to use Firefox as their primary Web application and browsing platform. StatCounter backs this up by indicating that within their data, 8.36% of visitors from the USA were on Macs, while 3.15% of visitors used Safari.
Trends to watch in the near future:

New browser releases (Firefox 3.1, Safari 4.0) and their effect on browser distribution
Uptake of MSIE 8.0 once it is released via Windows Update
Browser distribution is Asia

Does the browser really matter?

2009-02-25 / spierzchala / 6 Comments

Last fall it was Chrome. Now it’s Safari 4 Beta. Soon it will be Firefox 3.1 and IE 8.

Each browser has its harsh critics and fervent supporters. But in the end, does the browser really matter?

The answer to this question depends on who you speak to. Developers will say yes, because browsers make their lives hell, as none of them subscribe to the same set of standards for display, rendering, or code processing. I would bet that if you asked any developer, they would prefer that only one browser existed and was used by everyone.

The people at the end of the browser chain, you and I, don’t really care either. We only care when the browser drops an unexpected rendering surprise on us, or doesn’t work because the JavaScript functions were designed with Browser A and B in mind and we use C and the submit button on our purchase doesn’t work.
The question isn’t Does the browser matter? but Why does the browser still matter?

There is no reason to have five large browsers out there. There is no reason why they should all behave differently, render pages in their own unique way.

And while people will say that having multiple versions of multiple generations of uniquely developed browsers drives innovation and prevent stagnation in Web development, I say enough is enough.

There is no reason to have yet another browser. The browser doesn’t matter.

The content matters.

And when you switch the perspective around to that view, you should easily realize that the browser, any browser, is simply a window into the content being created for and by us. It should not matter to anyone that I use Opera, Safari, Firefox, IE, Camino, Chrome, or Lynx.

What does matter is that the content can be delivered to me the way I want it. Not the way the browser wants it.

What we need to realize is that browsers no longer matter. They are software. They are portals into what we are trying to do and say.

The browser is not the application; the Web is the application.

Browser Wars II: Why I returned to Firefox

2008-09-07 / spierzchala / 2 Comments

Since the release of Google Chrome on September 2, I have been using it as my day-to-day browser. Spending up to 80% of my computer time in a browser means that this was decision which affected a huge portion of my online experience.

I can say that I put Chrome through its paces, on a wide-variety of sites, from the simple to the extremely content-rich. From the mainstream, to the questionable.
This morning I migrated back to Firefox, albeit the latest Minefield/Firefox 3.1alpha.

The reasons listed below are mine. Switching back is a personal decision and everyone is likely to have their own reasons to do it, or to stay.

Advertising

I mentioned a few times during my initial use of Chrome that I was having to become used to the re-appearance of advertising in my browsing experience [here and here]. From their early release as extensions to Firefox, I have used AdBlock and AdBlock Plus to remove the annoyance and distraction of online ads from my browsing experience.

When I moved to Chrome, I had to accept that I would see ads. I mean, we were dealing with a browser distributed by one of the largest online advertising agencies. It could only be expected that they were not going to allow people to block ads out of the gate, if ever.

As the week progressed, I realized that I was finding the ads to be a distraction from my browsing experience. Ads impede my ability to find the information I need quickly.

Older Machines

My primary machine for online experiences at home is a Latitude D610. This is a 3-4 year-old laptop, with a single core. It is still far more computing power than most people actually need to enjoy the Web.

While cruising with Chrome, I found that Flash locked up the entire machine on a very regular basis. Made it unsuable. This doesn’t happen on my much more powerful Latitude D630, provided by my work. However, as I have a personal laptop, I am not going to use my work computer for my personal stuff, especially at home.

I cannot have a browser that locks up a machine when I simply close a tab. It appears that the vaunted QA division at Google overlooked the fact that people don’t all run the latest and greatest machines in the real world.

Auto-Complete

I am completely reliant on form auto-completes. Firefox has been doing this for me for a long time, and it is very handy to simply start typing and have Firefox say “Hey! This form element is called email. Here are some of the other things you have put into form elements called email.”

If you can build something as complex as the OmniBox, surely you can add form auto-completes.

The OmniBox

I hate it. I really do. I like having my search and addresses separate. I also like an address bar that remembers complete URLs (including those pesky parameters!), rather than simply the top-level domain name.

It is a cool idea, but it needs some refining, and some customer-satisfaction focus groups.

I Don’t Use Desktop-replacing Web Applications

I do almost all of my real work in desktop-installed Web applications. I have not made the migration to Web applications. I may in the future. But until then, I do not need a completely clean browsing experience. I mentioned that the battle between Chrome and Firefox will come down to the Container v. the Desktop – a web application container, or a desktop-replacing Web experience application.
In the last 48 hours, I have fallen back into the Web-desktop camp.

Summary

In the future, I will continue to use Chrome to see how newer builds advance, and how it evolves as more people begin dictating the features that should be available to it.

For my personal use, Chrome takes away too much from, and injects too much noise into, my daily Web experience to continue to use as the default browser. To quote more than a few skeptics of Chrome when it was relased – “It’s just another browser”.

Google Chrome: One thing we do know… (HTTP Pipelining)

2008-09-02 / spierzchala / 7 Comments

All: If you got here via a search, realize this is an old post (2008) and that Chrome now supports HTTP Pipelining and SPDY HTTP/3. Thanks, smp.

As a Web performance consultant, I view the release of Google Chrome with slightly different eyes than many. And one of the items that I look for is how the browser will affect performance, especially perceived performance on the end-user desktop.

One thing I have been able to determine is that the use of WebKit will effectively rule out (to the best of my knowledge) the availability of HTTP Pipelining in the browser.

HTTP Pipelining is the ability, defined in RFC 2616, to request multiple HTTP objects simultaneously across an open TCP connection, and then handle their downloads using the features built into the HTTP/1.1 specifications.

I had an Apple employee in a class I taught a few months back confirm that Safari (which is built on WebKit) cannot use HTTP Pipeling for reason that are known only to the OS and TCP stack developers at Apple.

Now, if the team at Google has found a way to circumvent this problem, I will be impressed.

Internet Explorer: Plan to completely support RFC 2616 anytime before the next ice age?

2007-03-13 / spierzchala / 0 Comments

I am writing up a client presentation for next week, and I just realized just how flawed Internet Explorer is. Microsoft claims that the browser is standards compliant. Yet it still doesn’t support HTTP pipelining.

And the frustrating part? They won’t tell us why. I have my suspicions, which include TCP stack issues and a flawed HTTP handling mechanism that is still based on Windows 95 architecture, but an explanation from Redmond would be nice.

Every (and I mean every) other browser can do this.

Microsoft, it’s time you detached your Web browser from your OS, like you’ve forced everyone else to do.

Private-Label Browsers and comments on a lost “browser war”

2005-02-18 / spierzchala / 0 Comments

Looks like Firefox could become the genesis of the private-label browser, unencumbered by nasty platform/OS/Service Pack limitations. [here — courtesy of the XSLT:General blog]

I believe strenously that Microsoft has committed a serious error in limiting the upcoming MSIE 7 update to Windows XP SP2 machines. It will not drive the large corporate IT departments who still use Windows 2000 to upgrade. It will increase resentment towards the company, which will be actively commented on in places (such as here).

I use Windows XP SP2. But as you see from the sub-title of this blog, the next computer I will buy for myself is going to be a Macintosh Powerbook. And I will run Safari, Firefox, Camino, and (very, very occasionally) fire up some 6 year-old, badly maintained version of MSIE for MacOSX.

When I use Windows, I will use MSIE to compare the look and feel of the pages I build. And nothing more.

If Microsoft wanted this new browser to be a true update, and not simply an addition to their program of forced obsolescence, they would have made it free of OS restrictions. What Microsoft has said is that if you don’t run Windows XP SP2, your browsing experience will be sub-optimal, less secure, and unsupported.

Web designers, this means that you will have to have yet another platform to test your Web designs, as MSIE 5.5, 6.0, and 7.0 will all interpret CSS, CSS2 and other design features differently.

So, what is the big deal about MSEI 7.0? It shows the Web community that Microsoft has still not learned the lesson that Firefox is teaching: be everywhere. Microsoft, the OS is not the platform of the future; the browser is the platform of the future. And a browser that can run anywhere, anytime, in any language, on any hardware, will win.

Difference of Opinion

2005-02-04 / spierzchala / 0 Comments

Port80 Software in San Diego is a team who is dedicated to improving Web performance.

However, they just recommended Maxthon, which uses the MSIE engine. [here]
I can’t buy into that. It still uses a core browser which has been patched but has not evolved since 1999. Until Microsoft releases a browser that can handle HTTP Pipelining — don’t understand why it can’t do it…unless there is a technical reason — I will stick with Firefox.

Browser Percentage Art

2004-12-26 / spierzchala / 2 Comments

I thought everyone would get a kick out of my mirror image browser percentage chart.

What do you see in the picture?

Firefox Rising

2004-12-14 / spierzchala / 0 Comments

MozillaZine has some interesting statistic war data on the Firefox arrival. Now of course Microsoft is disputing the numbers. But it is sort of like arguing that the Sammy Sosa Home Run record doesn’t mean as much as the Roger Maris or Babe Ruth Records because of the extended season.

Microsoft has lost this battle. If they are willing to suck it up and try to win the war, they have to agree to the following:

Internet Standards — CSS, XHTML, RSS, and HTTP/1.1 — do matter. In fact, when looking at Web performance, I have to fall back to the following argument: “I don’t care if MSIE does it, it is not in the accepted standards”. Microsoft has a very active research division that has participated in the development of these standards. Means they must buy into them at some level.
MSIE hasn’t had any buzz since the start of the pop-up wars.
MSIE suffers from a general perception of being insecure. Microsoft hates when the others can effectively use FUD against their products.
Being multi-platform has it’s advantages. And Macintosh doesn’t count, especially since you don’t have a current version of your browser for OSX. Geeks use Linux, and OSX, and BSD, and Windows. But Geeks all love Firefox, and that runs on ALL platforms. So do 90% of the extensions and themes.

I like Firefox. But I do not underestimate the power that Microsoft can bring to bear if it wants to really develop a kick-ass browser. And in the end, all Web users win.