Embed Notice

@sorenladegaard @christianschwaegerl @Vivaldi

We have the experience of having built our own engine at Opera. It was called Presto and it was great. Best engine out there, IMHO, but we ran into issues where we were being blocked from accessing content. Often by competitor sites, but also others.

I would have loved to build another engine, but there is a reason why Apple, Google, Microsoft and others decided not to do that and use an open source browser core. Thus we did the same. Building another engine from scratch is just not feasible for us.

Given our experience with Opera, it would also be important to go with what most are using, so going with Chromium made sense. Less compatibility issues.

The other option would have been Gecko, but at the time that we made our decision, Gecko was going through significant rewrites.

I have also understood, that Mozilla is not always thrilled with competitors using their code. They are a highly competitive company.

There are a lot of issues with using Chromium, but we still believe it was the right choice. We have made a lot of patches, 2000 files, and we have added a lot of our own code on top.

Vivaldi is unique. We have a lot of functionality you find nowhere else and plenty that we originated. I hope you enjoy it.