Vivaldi: Another contender to the array of Webkit-derived browsers

This post was published in 2015 and is kept here for reference. It may contain information that's outdated or inaccurate. All external links and references have been updated to point to archived versions on archive.org where possible.

Earlier this week a new browser called “Vivaldi” sprung up across many of my early-morning technology news feeds.

I managed to put off trying it out for a couple of days, due to my being too busy, and agreeing with many of the pessimistic comments that were strewn across the release announcement posts.

The announcement was met with some derision…

  • “Who are these “Vivaldi” people and why would ‘Our friends’ need a new browser?”
  • “Oh this is just another webkit wrapper”
  • “Bundling Mail and all of that in the browser? Hello Netscape 2015!”
  • “The website doesn’t even have any screenshots, why would I download this?”

If you spend a minute to read the introductory section on the Vivaldi website, you’ll discover that it’s not a new team as such, but actually an old team longing to bring a product back to it’s roots.

The team in question? Some of the folks from Opera. The browser? Their vision for where Opera should be today, including the expected integrated mail and other features that long-time Opera users are used to, but have been missing since Opera moved to Webkit (and since Opera 15, Blink) back in 2013.

Vivaldi is using Blink at it’s core, but in your face you’ll find a simple bold interface. It’s powered by node.js and React, and doesn’t appear to be using much in the way of native UI components.

This lack of native UI is particularly disjointing, as it means the browser window doesn’t look like other applications on OS X, and doesn’t “feel” right.

Visiting a couple of different sites in Vivaldi, you’ll notice that the interface is more of a chameleon than anything, taking on the prominent colour from the favicon of the page you’re viewing to style the toolbar and active tab.

It would be interesting if this could support the <meta name="theme-color" /> tag in the future, to allow developers to set a specific colour for the interface.

As a front-end developer, it’s a pain to have another variation of a browser in the mix, because if it gets any serious uptake it’ll mean an additional browser to test things in.

Right now it’s using Blink (537.36), so it should be identical in rendering to Chrome, and I hope it doesn’t deviate too far from Chrome in the future!

This is just a “Technology preview”, and as such it lacks a lot of features, but it’s nice to see that this is being worked on!

This post is also available in plain text

[Comments]

Want to comment? You can do so via Github.
Comments via Github are currently closed.

[Webmentions]

Want to reply? I've hooked up Webmentions, so give it a go!