We don’t publish it under an open-source license and only release obfuscated versions of it. As such, it is our most valuable asset in terms of code. The Vivaldi UI is truly what makes the browser unique. If Vivaldi browser is so close to being released under a unified open-source license, why isn’t it? This means that roughly 92% of the browser’s code is open-source coming from Chromium, 3% is open-source coming from us and only 5% is our UI closed-source code. Of the three layers, only the UI layer is closed-source. Licenses for this can be found in the source package and in the installed browser by navigating to vivaldi://credits. Details are explained in the README and LICENSE files within the package. The changes are published under an open-source BSD license. A copy of Vivaldi browser’s open-source code is available on our website. This makes our internal process easier because it lets us build everything – Chromium and our C++ code – in one library. We also publish all our C++ feature backend code as if it were part of the Chromium changes. Chromium itself has an open-source license and all the changes we make to it in order to support our UI layer and features get published. On Android, the UI is implemented in Java and is mostly derived from the Java UI included in Chromium (the license of the Chromium Java code doesn’t require us to publish changes made there).On desktop, the UI is written using mostly HTML+CSS+JS.These two layers support our UI, which comes in two different flavors. ![]() On top of Chromium, we have a lot of backend C++ code to support our features, such as Ad blocker and Notes. ![]() Vivaldi is built in roughly three layers.Īs most people know, we use Chromium as a foundation for our browser. Vivaldi browser is part open-source, part closed-sourceīefore we go into open-source, here’s a brief reminder of how Vivaldi browser is built. However, as with everything, it becomes a lot more complicated when you look at the details. We have a lot of understanding for this point of view and this is a question we regularly struggle with internally, as many of us are proponents of open-source and use open-source software. ![]() We’re providing Vivaldi for free, we make money from searches and partner deals, therefore allowing external people to have access to and potentially help with the source code shouldn’t be any trouble, right? To many people, the question of releasing Vivaldi browser’s source code under a unified open-source license seems to be clear-cut. Read this article in Español, Русский, Français, Deutsch, 日本語.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |