← All 12 chapters

Chapter 08

Opera and other independent alternatives

Beyond Netscape and Internet Explorer, a world of small browsers flourished. Opera, Konqueror, K-Meleon and iCab showed that speed, freedom and clever features did not have to come from the largest camp.

Small, fast and independent · 1994–2007

There was a world beyond the browser war

The first browser war looks like a two-way contest in retrospect: Netscape versus Microsoft, Navigator versus Internet Explorer. Yet anyone who looked beyond the default—in a computer magazine, on a download site or on a Linux desktop—found a much richer choice. Some browsers were built for one operating system; others aimed above all to be smaller, faster or more adaptable.

Their market share remained modest, but their ideas were substantial. They showed that a browser was not a law of nature. Buttons could live elsewhere, several pages could fit inside one window, and users could decide whether images, formatting or advertising deserved scarce screen space.

Two Norwegians start again

In April 1994, Jon Stephenson von Tetzchner and Geir Ivarsøy began work on a research browser at Norwegian telecom company Telenor. The project was initially called MultiTorg. When they continued the work outside Telenor, Opera Software emerged. The first public Windows release arrived in 1996.

Opera took a different position from the free browsers supplied by large platform companies. It was sold as independent software. That forced its makers to offer a clear reason to choose it: a compact installation, fast controls, extensive settings and versions for a wide variety of systems.

1994MultiTorg

A browser research project begins at Telenor in Norway.

1996Opera 2

The first public Windows version appears.

2000Opera 5

A free advertising-supported version lowers the threshold.

2001Opera 6

More customisation and a broader international rollout.

2003Opera 7

The new Presto engine takes over rendering.

Small was a design choice

On a slow PC and a dial-up connection, every second counted. Opera presented itself as small and fast, but compactness meant more than a download with few megabytes. It gave users direct control over what loaded. Images could be switched off, pages could be zoomed and toolbars could be customised extensively.

It was not a miracle cure. Sites made only for Netscape or Internet Explorer could break in Opera. Choosing an alternative browser could therefore mean working faster while more often meeting a notice that your browser was unsupported.

A browser as a Swiss Army knife

Opera brought many tools together: browsing, bookmarks, downloads and later email and news feeds. Its early interface used a workspace in which several document windows could sit inside the main window. It was not exactly the modern row of tabs, but it made switching between pages much faster than hunting for separate windows.

01Multiple pages

Document windows and later tabs kept a session together.

02Mouse gestures

A short movement could go back, close or open a new page.

03Zoom and styles

Pages could adapt to the screen and reading preferences.

04Saved sessions

Open pages could return after the browser closed.

Free, but with a strip of advertising

Until 2000, Opera was mainly shareware: you could try it, but continued use was supposed to be paid for. Opera 5 for Windows changed the model. It was free to download, but displayed advertising in the interface. Registration removed the ad strip.

OPERA 5.0 — CHOOSE YOUR VERSION
FREEWith advertising

Download and use immediately.

OR
REGISTEREDMore room for the Web

Payment removes the adverts.

Free reconstruction of the distribution model in 2000.

It was a striking compromise. The browser became more accessible, but the promise of a compact interface visibly clashed with a banner above the page. In 2005, advertising disappeared from the desktop browser. Opera remained free and had to distinguish itself entirely through features, speed and versions for other devices.

Konqueror merged the Web and files

On Linux, alternatives grew from a different starting point. KDE 2.0, released on 23 October 2000, introduced Konqueror as both a web browser and file manager. An internet address and a folder on the hard disk could open in the same kind of window. This suited the open-source idea of a desktop assembled from cooperating parts.

Konqueror showing the German Wikipedia, toolbars and a side panel
Konqueror in 2005, shown with Wikipedia and a side panel. Image: KDE, Wikipedia and Daniel Arnold, via Wikimedia Commons, CC BY-SA 4.0.

Konqueror's KHTML engine was small, open and technically influential. The browser itself never dominated the consumer market, but it showed that an independent web engine could emerge from a desktop community—not only from an American software company.

K-Meleon and iCab chose their own home turf

Not every alternative built everything itself. K-Meleon combined Mozilla's Gecko engine with a lightweight, highly customisable Windows interface. Users gained the web compatibility of the Mozilla project without the full Mozilla suite. On the Mac, iCab offered its own shareware browser from 1999, recognisable by its taxi icon and abundance of settings.

K-Meleon 0.8 showing a Wikipedia page and classic Windows toolbars
K-Meleon 0.8 in a classic Windows environment. Image: Kaszeba, via Wikimedia Commons, CC BY-SA 3.0.
WINDOWSK-Meleon

A light Windows shell around Gecko, focused on speed and customisation.

MACiCab

Shareware with many tools, extensive control and its own identity.

KDE / UNIXKonqueror

Browser and file manager inside one open desktop environment.

The engine underneath the window

These browsers made an important distinction visible: the browser window and the engine underneath are not the same. K-Meleon used Gecko, Konqueror used KHTML and Opera had its own Presto. The interface determined how you worked; the engine determined how HTML, CSS and scripts were interpreted.

Buttons, menus and tabsINTERFACE↕Process HTML, CSS and JavaScriptRENDERING ENGINE

That distinction later became decisive. New browsers could combine an existing engine with a different experience, while a small engine could unexpectedly become the basis for much larger products. Browser history is therefore not only a row of logos, but also a family tree of shared technology.

Not the winner, still the inventor

Opera and its contemporaries did not win the browser war. Yet they kept the market moving. They proved that users could ask for recoverable sessions, more pages in one window, zooming, mouse gestures and extensive customisation. Features that first seemed eccentric later became ordinary.

Their legacy is cultural too. Choosing a browser became a statement about what mattered to you: speed, open source, a familiar desktop or complete control. In the next chapter, that appetite for an open alternative reaches a much larger audience as Mozilla grows into Firefox.

Sources