OK, so you want a web anyone can use, whether they’ve picked Windows, Macintosh, Linux, or whatever came on their cell phone or PDA. What can you do? Here are some ideas:

Web Users

Try an alternative browser. Use it exclusively for several days. Get used to what it can do, and how it differs from Internet Explorer or the browser you’ve been using.

Better yet, try two. If you already use Firefox, try Opera. If you already use Opera, try Firefox or Chrome. You can always switch back if you like the other one better. The goal is to see what’s out there.

If you find a web browser you like, tell your friends and family. Get them to try it out, or give them a demo.

If you really like the browser, and would like to spread awareness, consider joining a promotional group like Firefox Affiliates or Choose Opera.

Bloggers and Content Providers

Write about your favorite web browser. Encourage your visitors to try it out. Post links or buttons pointing to the download site.

If you agree with the Alternative Browser Alliance‘s goals, feel free to link to us.

Web Developers

Base your design on web standards whenever possible. Take a look at sites like the CSS Zen Garden and A List Apart for ideas. The Mozilla Developer Center and Opera Developer Community are also good resources.

Validate your code. Learn which rules are safe to break. Where you have to use proprietary features, use graceful degradation so that other browsers at least get a usable experience. Some tools for validation include:

Try not to make assumptions based on browser detection, which is often wrong by the time the next version of a program rolls around. Where you have to check, detect capabilities, not browsers.

Start a collection of web browsers. When designing a site, check the layout with as many browsers as you can early in the process. Check critical parts of the site before you go live. Sites like Browsershots or BrowserStack can help you with browsers and platforms you don’t actually have.

Do your development on Chrome or Firefox. Both have extensive tools to help you test and debug your websites.

Conclusion

These are just suggestions. You can do as much or as little as you want, as much or as little as you can!

This article originally appeared on the Alternative Browser Alliance in 2005. This is the latest version before I retooled the site a decade later.

The main reasons are innovation and security.

The intense competition between Netscape and Internet Explorer in the late 1990s ended with the World Wide Web dominated by one browser. At its height, Internet Explorer was used by an estimated 95% of people online.

There were many reasons IE took over: it came free with Windows, the most common operating system. Many webmasters would rely on Internet-Explorer-only features like ActiveX, leaving their sites inaccessible to people using other web browsers. As time went on, webmasters would write their web pages without checking for errors, except by testing them in Internet Explorer.

One Browser, One Web… One Target

You might think this is acceptable: One vision, leading the web forward. Unfortunately, once Internet Explorer’s dominance was secure, Microsoft did very little to update it. There was almost no innovation from 2001 through 2004, either in the front-end or the back-end, until Windows XP Service Pack 2 redesigned security. Many aspects of the languages that make up the web, particularly in the core languages of HTML and CSS, remained unavailable or buggy in IE until the 2006 release of version 7—5 years later—and even IE7 still has a long way to go.

Also, not everyone could or wanted to use Internet Explorer. Die-hard Netscape fans clung to their browser or shifted to Mozilla. People using Linux-based or Unix operating systems didn’t even have the option of using IE. Macintosh users could use Internet Explorer, but their version had different quirks than the Windows version everyone used for testing.

Two things happened.

First, the smaller browsers started innovating. While the heavyweights battled for dominance, a tiny Norwegian company called Opera began to re-think the way people used a web browser. Long after Internet Explorer and Netscape were free, Opera was still shareware…and still getting paid customers. (Today Opera’s free too.) Mozilla, a spin-off of the old Netscape, made an effort to implement as much of the web standards as possible, as correctly as possible. A small project called NetCaptor combined MDI with tabs to create “tabbed browsing,” which made its way into Opera, Mozilla, Firefox, Safari… and has finally appeared, years later, in Internet Explorer 7.

Second, the Internet ceased to be a friendly neighborhood and was flooded with viruses, trojan horses, and spyware. With a single program accounting for more than 90% of users, and a design that tied that program directly to the operating system, that meant one set of security bugs could attack most of the users on the internet. Alternative browsers and operating systems have long promoted their security over Windows and Internet Explorer. In 2004, people who used a Mac, Linux, or an alternative browser on Windows didn’t even need that extra level of protection because they weren’t even targets!

The Solution

Competition keeps innovation going. If several products have to fight for market share, they have to continually one-up each other. End result: all browsers improve, everyone wins.

It hardly seems a coincidence that Microsoft stopped developing Internet Explorer when they trounced Netscape, then started again as soon as Firefox started making gains.

Security may be easier to manage when you only have one place to look, but it’s also easier for the bad guys to crack. In 2004, they could get 90% of the web just by targeting Internet Explorer on Windows. In 2008, they can still get 75-80%, still aiming at one target. Now imagine that spread out among IE, Firefox, Opera and Safari on Windows, PowerPC Macs, Intel Macs, and Linux. They’d have to settle for 10% or try to crack every combination they could. Web developers, on the other hand, designing for the common language of the web, would have no more trouble than they do today.

And who knows? You just might find yourself liking another browser better than you thought!

This article originally appeared on the Alternative Browser Alliance in 2005. This is the latest version before I retooled the site a decade later.

I’m launching a new browser switch site, with a bit of a twist. It’s promoting all alternative browsers, kind of like Browse Happy, but a bit more inclusive and aimed at a slightly different audience.

The idea is that a diverse browser “market”—one with three or four major browser suppliers all competing with each other—is the best way to maintain innovation and security. Anyone following the classic browser wars, the lull in IE development, and the sudden appearance of IE7 can see the difference competition makes for innovation. As for security… If someone can hit 90% of the world’s computers by hitting IE on Windows, we’re in trouble. But if they have to hit 30% each on IE, Firefox, and Opera, and even those are split among Windows, Mac and Linux, it’s a lot more effort for the bad guys.

I got the idea back in May, during some rather heated Firefox/Opera flame wars. It seemed to me that fans of the two browsers had more in common than they thought, if they’d just stop fighting each other. I worked on it during June, and launched a test version last month, asking for feedback from friends and from the Spread Firefox and My Opera communities*. It’s still not where I’d like it to be (Comic-Con, then procrastination), but after the net went crazy over Paul Thurott’s “Boycott IE” article I realized I’d better launch what I had and refine it later.

So, without further ado, I’m officially launching the Alternative Browser Alliance.

Alternative Browser Alliance

*I’ve since imported my comments from the post on Confessions of a Web Developer, my old blog at My Opera, because it was largely the same content. That’s why some of the comments here are dated earlier than this post.

The ridiculous Firefox/Opera rivalry (it’s software, not religion) has given rise to one annoyingly persistent meme: the belief that tabs are just MDI (Multiple Document Interface).

They’re not.

MDI, as implemented in many Windows applications and eventually abandoned by Microsoft, involves having a mini-desktop inside your application, with its own windows that you can minimize, maximize, and rearrange. If you have a taskbar-like interface it can look a lot like tabs, and you can certainly use it the same way as tabs, but it’s a different UI paradigm.

A tabbed interface is very specific. You have only one view at a time in your application window, and you switch between them based on a row (or column) of tabs along the window’s edge. You can look at it as a proper subset of MDI, but it is not the same thing.

Additionally, classical MDI uses one master window for the application. All documents appear in that window. Tabbed interfaces often (though not always) allow you to have more than one window, each with its own set of tabs. This makes it possible to group documents, web pages, etc. by category in a way that you can’t with a single-document interface or classic MDI.

So when people claim Opera had tabs first, they’re thinking of MDI—which Opera did have before Mozilla did. Tabs were showing up in browsers like Netcaptor and Galeon, however, long before they showed up in the Mozilla suite—and long before Opera hid its MDI capabilities under a tab-like veneer.

(reposted from Spread Firefox in response to Asa Dotzler’s post on the history of tabbed browsing)

The new Opera 8.0.1 includes an experimental feature called Browser JavaScript. It’s a collection of client-side scripts that automatically corrects known errors on websites as they’re displayed. Opera downloads updated scripts once a week.

It’s an extension of the User JavaScript concept. Firefox’s Greasemonkey is basically the same thing, and it’s gotten a lot of attention as a method for correcting or enhancing sites. The key difference is that these scripts are centrally maintained, and automatically updated.

Browser JavaScript is disabled by default, and can be turned on by putting Browser JavaScript=1 in the [User Prefs] section of your opera6.ini file.

(via Opera Watch)

Opera BrowserThere’s a saying about the elephant in the room that no one will talk about. Everyone knows it’s there, but by some unspoken rule no one will mention it. I’ve noticed that when web browsers are compared, there’s one thing Opera supporters tend to ignore or downplay: Opera’s business model.

Internet Explorer and Safari are bundled with their respective operating systems, and so they’re perceived as free. Firefox is free in both the gratis and libre senses of the word. Opera, however, is ad-supported by default and will disable the ads if you pay for it.

You can use Opera without paying money, but you’re still paying it in attention (a persistent chunk of space dedicated to advertising), so in comparison to the other three leading browsers, it’s perceived as being less free. Think of it in terms of television.

So the perception of cost looks like this:

  • IE, Safari, Firefox (commercial-free TV)
  • Ad-supported Opera (network TV)
  • Paid-for Opera (cable or satellite)

Most people really do prefer free without ads to free with ads or paid subscriptions. Why else is skipping commercials one of Tivo’s most popular features?

I’m certain this impacts marketshare, and it definitely impacts media coverage. Just look at CNET’s recent IE vs. the world review. Opera 8 gets high marks for features, but what’s the summary? “Despite a ton of great technology in Opera, few consumers will be likely to pay for the app. ” Whether you think the review is otherwise fair or not, the business model clearly lowered it several notches on the reviewer’s scale.

Next: Firefox’s blind spot.

Disclaimer: I’m a regular Firefox user these days, but I’ve also paid to register Opera since version 3.5 was current back in 1999. I used Opera as my main web browser on Windows back when Netscape 4 was aging and Mozilla hadn’t yet stabilized enough to replace it.

Sorry for the misleading title, it’s sort of an homage to CNET’s recent coverage of Firefox.*

Opera CEO Jon von Tetzchner, excited by the response to Opera 8.0, promised to swim from Norway to the US if Opera 8.0 managed 1 million downloads in 4 days. (By comparison, Firefox 1.0 managed 1 million in less than a day, and hit 2.5 million by the end of day 2.

Well, they did it, and von Tetzchner has donned a wet suit [CNET].

Tetzchner entered the “freezing Oslo fjord” on Monday and started swimming toward the United States, the company said. Opera’s public relations manager, Eskil Sivertsen, is rowing an inflatable boat alongside Tetzchner “as an act of guilt after making the CEO’s statement public,” according to the Opera Web site.

Full details, photos, and a map are at Opera.com/swim. [archive.org]

Update two days later:

Let me tell you, those PR folks at Opera know how to set up a publicity stunt.

In a “dramatic” update to the saga, Opera’s CEO won’t finish swimming to America after all, as his PR manager’s raft deflated an hour into the day’s swim.

Some choice quotes:

“As much as I don’t want to talk behind a colleague’s back, there is no doubt that we would never have let Eskil assist Jon in the raft had we known he can neither swim nor read maps,” says an embarrassed Tor Odland, Opera’s Communications Director. “I feel partly responsible for letting Jon down, as he cannot possibly continue without the raft.” [emphasis added]

A local farmer spotted the drama from his kitchen window and took surprisingly sharp photos with a remarkably powerful telescopic lens.

“And my mother [in Iceland] will be so disappointed when I call and tell her that I won’t be stopping by for hot chocolate after all.”

The tongue-in-cheek tone of the whole thing is right up there with the Opera Bork Edition that translated the MSN website into the Swedish Chef’s unique form of gibberish. That was to point out the ridiculousness of MSN singling out visitors using Opera and sending them a broken—or perhaps we should say borken—page.

It’s kind of funny how Opera can get away with stunts like this. Microsoft or Apple would be embarrassed to even consider it, and Mozilla wouldn’t dare. These days Mozilla/Firefox is too busy fighting uphill for respect. They wouldn’t risk sanctioning the “Always use Protection” poster, and they wouldn’t try something this wacky. Whatever happened to the days when the IE team deposited a big blue “e” on Netscape’s front lawn?

*Things like “Mozilla flaws could allow attacks, data access” which didn’t just bury but actually omitted the fact that a fixed version had been released three days earlier, and that the disclosure was made as part of the release. The second-to-last sentence, “All versions of Mozilla Suite prior to version 1.7.7 and all versions of Firefox prior to 1.0.3 are vulnerable.” sort of hints at it, if you know that these are the newest versions, and if you don’t misread it as “through” instead of “prior to.” And the original article on the Opera swim promise misstated the Firefox download numbers using one of the preview releases instead of the big launch, claiming it took 5 days to reach 1 million. They’ve “corrected” it to “within days,” which is technically true—but wouldn’t “in less than a day” be more accurate and better convey the contrast? Compare this to other articles from last week like “Apple patches iSync flaw” and “RealNetworks fixes ‘highly critical’ flaw” and you have to wonder whether there’s a misinformation campaign some editorial bias involved.

»All pages site-wide with this tag