For years, Opera was the internet’s quirky innovator, pioneering features we now take for granted. But a single, pragmatic decision in 2013 fundamentally altered its DNA, steering its future down a path that was almost completely different.
The All-in-One Powerhouse
To understand
the shift, you have to remember what old-school Opera was. Long before Chrome dominated the landscape, Opera was a trailblazer. It introduced tabbed browsing to the world and was known for being a lean, fast, and feature-packed suite of tools. Its identity was built on its proprietary rendering engine, Presto, which was the browser's heart and soul. This wasn't just a browser; for many power users, it was a complete internet command center. The jewel in its crown was M2, a sophisticated and fully integrated email and news client. You didn't just browse the web; you managed your entire digital life—email, RSS feeds, and browsing—from a single, unified window. This all-in-one philosophy was Opera's signature, a testament to its ambition to be more than just a window to the web.
A Web Built for Someone Else
Despite its innovations, Opera faced a relentless, uphill battle. By the early 2010s, the web was rapidly standardizing around a different engine: WebKit, the open-source project powering both Apple's Safari and Google's burgeoning Chrome browser. As Chrome's market share exploded, more and more developers began coding specifically for WebKit, often ignoring or poorly testing for other engines like Presto. For Opera users, this meant encountering broken websites and compatibility issues that weren't their browser's fault. Internally, maintaining the Presto engine became an increasingly expensive and resource-draining fight against the tide. The company faced a difficult choice: keep pouring resources into maintaining its unique engine for a web that was increasingly hostile to it, or make a radical change.
The Great Chromium Switch
In February 2013, Opera announced its decision: it was abandoning Presto. Starting with Opera 15, the browser would be rebuilt from the ground up using the open-source Chromium project—the same foundation as its rival, Google Chrome. The logic was purely pragmatic. By adopting Chromium's Blink engine, Opera would instantly solve its compatibility problems and gain access to the vast library of Chrome extensions. It would also free up its developers to focus on creating unique user-facing features instead of constantly playing catch-up on rendering standards. From a business and technical perspective, it was a sensible move. But for the browser's identity, it was a seismic shift. The very core that made Opera 'Opera' was being surgically removed and replaced with the heart of its biggest competitor.
What Was Gained, and What Was Lost
The new Chromium-based Opera was fast, modern, and compatible with virtually every website. But it wasn't the same. The rewrite meant that many of the beloved features from the Presto era were gone, at least initially. Most notably, the M2 email client was ripped out. Opera claimed the feature was too deeply integrated with the old Presto engine to be easily ported over. It was eventually released as a standalone program, but for users who treasured the all-in one experience, the magic was gone. The browser's history was cleaved in two: the pioneering, everything included Presto era, and the modern, compatible, but more conventional Chromium era. It ceased being a self contained internet suite and became, in the eyes of many long time fans, another 'skin' for Chrome, albeit one with its own clever features. The browser that 'almost' was would have been a continuation of that integrated, power user dream.
