Opera founder unveils feature-rich Vivaldi power browser

Almost two years ago, the Norwegian browser firm Opera ripped out the guts of its product and adopted the more standard WebKit and Chromium technologies, essentially making it more like rivals Chrome and Safari. But it wasn’t just Opera’s innards that changed; the browser also became more streamlined and perhaps less… geeky.

Many Opera fans were deeply displeased at the loss of what they saw as key differentiating functionality. So now Jon von Tetzchner, the man who founded Opera and who would probably never have allowed those drastic feature changes, is back to serve this hard core with a new browser called Vivaldi.

Old meets new

Vivaldi doesn’t mark a return to Opera’s old internals – it uses Chromium as a base and has a user interface that is itself unusually built using web technologies – but it does bring back features such as tab stacking, an advanced bookmark manager, keyboard shortcuts and the ability to start with multiple session windows.

Opera used to be “more feature-rich, for a crowd of users that want more from their browser,” von Tetzchner told me:

After I quit [as CEO in 2010, then fully in 2011], Opera changed their philosophy. They made kind of a browser that’s more in line with most of the other browsers and doesn’t have a lot of features. The focus is in a way on making the browser disappear, and I think there’s a lot of people that want something different.

While these users could install Chrome with “30 extensions” to get all the functionality they want, von Tetzchner argued, now they can install Vivaldi and get everything in the main package.

Gigaom rendered on Vivaldi technical preview

Gigaom rendered on Vivaldi technical preview

Based on the quick play I’ve had with the first Vivaldi technical preview, publicly released on Tuesday, there’s more to it than just reviving the old Opera feel (though that’s a clear aim). For example, the HTML5-based UI allows the browser to rather neatly adopt the color scheme for the page being visited. The use of web technologies for the front end also makes it easier to launch cross-platform – the technical preview is available for Windows, OS X and Linux right from the start.

Future features

The “sister service” to the browser, the Vivaldi.net community suite, already launched quietly about a year back. This was in many ways a replacement for the old, ditched My Opera community, and it provides blogging and forum functionality.

“We believe it will be the natural playing ground for those that are using the browser, with a free mail service and a place you can put your photos,” von Tetzchner said, noting that the mail servers are based in Iceland. “It’s not really a commercial site; we haven’t spent a lot of time marketing it. But we will add more functionality and change it gradually.”

Von Tetzchner told me more new browser features will be revealed by the time Vivaldi reaches its first full version (WebRTC will likely be supported, for instance.) A mobile version is also in the works, though von Tetzchner wouldn’t say more on that subject than “We’re going for a browser that has more functionality than what you’re used to, but also has more different ways to do things – the principle of that will be the same on mobile as it is on desktop.”

The Vivaldi team numbers around 25, a “substantial part” of which is the technical team, and more than half of which are former Opera workers. Von Tetzchner is personally funding it all for now, but the browser’s business model will be the standard affiliate-deal affair.

Will Vivaldi be big? It’s hard to say – Opera itself hasn’t broke past a market share of a few percent for many years, apart from in the feature-phone market. But Vivaldi does seem to combine a fresh new look with an impressively old-school appeal to the power user, and it may well find its niche. Perhaps not everyone does want the browser to just disappear into the background after all.

Opera is back on Linux

Having dropped Linux support around the time of its root-and-branch revamp, Opera is now offering its first developer version for Linux users in over a year.

Non-Safari iPhone browsers will soon have access to Apple’s full-speed Javascript engine

One of the most obvious drawbacks of Apple’s(s appl) approach to iOS development has been the fact that no browser except for Safari could tap into Apple’s fastest Javascript engine. Not only did this decision prevent standalone browser apps like Chrome(s GOOG) from running at full speed, it also hampered apps like Twitter that need to open a lot of URLs. As noted in Re/code, this is changing in iOS 8: Apps using the latest WebKit interface will have access to Apple’s Javascript engine. Hopefully, this means users will soon be able to also set a new default browser as well, but we’ll see: iOS 8 may be significantly more open than previous versions, but Apple’s not going to radically change overnight.

GigaOM Reads: A look back at the week in tech

Its a unicorn. No it’s a phone. Actually it is Facebook Home, for now; Apple’s China Syndrome is making it think different; The Bit coin boom (& bust); Chrome & WebKit go to war and did Vdio really kill the Rdio star?

Browser realpolitik

If you didn’t think Google’s move to fork Webkit with its own engine Blink wasn’t going to make things a little messy on the browser front, think again.

That’s because – as I wrote for this week’s weekly update – the Webkit power-center mainly revolves around Apple now, and now, given Google’s move, the Webkit folks are looking to do a little house – or rather code – cleaning.

The email is from a software engineer at Apple, and it shows how Google’s move has already started to push the camps – and code bases – farther apart. While the initial target may be only code that is specifically for Chromium, as The Register points out, there are inevitably going to be those Webkit developers who rely on Google specific code like the V8 Javascript engine.

Long term, things will get messier and slightly confusing for companies as the balkanization around browser code continues. Just as Samsung could potentially be hurt by the removal of the V8 Javascript engine, just consider that they are also in bed with Mozilla for a next-gen browser engine themselves.

Bottom line, all of these bigger companies will have to manage multiple browser engines across multiple product lines in coming years until things shake out.  But, just as with politics, it seems all the big players are working behind the scenes in a game of browser realpolitik to gain an upper hand down the road.

Why is Opera moving to WebKit? Because it has to.

Opera has confirmed that it’s adopting the WebKit rendering engine and the Chromium framework. Why? Apple and Google have so much influence that the mobile web is being written to their specs.

Guess who is WebKit’s new best friend

WebKit technology is what powers some of the top browsers (especially mobile) today. While Apple and Google are its most visible champions, the support for WebKit and ancillary technologies is coming from unlikely quarters such as Amazon and Boxee. Here’s its new BFF.