In Vivaldi, you can pick a background color, an overall theme, play around with the address bar and tab positioning, as well as the Start Pages. It’s the Vivaldi code that makes it possible to customize the browser to the extent you are familiar with. Instead of using the normal Chromium UI, we focused on building our own based on web technologies. With the engine part out of the way, we forged ahead. The large community around the Chromium project also meant that Vivaldi could benefit from code improvements many developers – including ourselves – report and upstream (Vivaldi devs regularly report issues and are about to start upstreaming code). There is a reason why no-one has built a new engine from scratch in 20 years. Developing a new engine from scratch would not have allowed us to focus on what mattered to us the most – it would have taken far too long to do and required significant resources. Other pieces of code were either unavailable or undergoing significant re-writes. From the very beginning we’ve focused on building our own, highly customizable UI.īelow the UI of a browser – the part most people see and interact with – there’s a rendering engine responsible for displaying the requested content in the browser window, as well as a browser engine responsible for bringing together the rendering engine and the application’s UI.ĭifferent browsers use different engines and when it came to picking ours, we found that the Chromium engine code was secure and the most widely used – things that were important to us.
Vivaldi launched in 2015 to make up for the loss of features in other browsers. The truth is, while we rely on the Chromium engine (maintained by the Chromium project set up by Google), this is where similarities end. We often get asked about the relationship between Vivaldi and Google Chrome.
0 kommentar(er)
