Chromium Engine - Why doesn't Vivaldi use the latest one?
nickparkermusic last edited by Ayespy
I have a very humble knowledge about this, more like front page information, but I saw that Vivaldi is using Version 64 of Chromium while the latest Chromium is already at 67, I understand 67 is very raw and packed with bugs but why not Version 66? And how often Vivaldi's engine get updated to newer Chromium?
Hadden89 last edited by Hadden89
Vivaldi is based on blink - as any chromium - but it has also a totally different interface written by Vivaldi team to bypass chromium limitations (side tabs anyone?) and add new functions (themes ecc)
Clearly, this particular browser need to "patch" any chromium core version to accomodate to their UI, so will be always few versions behind any other chromium which use a vanilla chromium - so blink and their ui.
Vivaldi also can decide to skip a particular chromium core version if severe issues are known and go with the newer - that could be older than the "current" one.
@nickparkermusic Roughly every six weeks is what I read somewhere here. Vivaldi have to retest their code with each new release of Chromium, so it is always going to be a month or two behind the leading edge.
Any critical security updates are implemented more quickly, much to the chagrin of some users, as this tends to introduce a number of regressions. That's what one should expect, especially of Snapshots, but it may also happen with finals when a premature update of Chromium has to be made for security reasons.
According to the Chrome Download Page
Current stable version (Google Chrome): 65.0.3325.146 (530369) • Tuesday, 6 Mar 2018
@nickparkermusic Chromium 67 can be downloaded, but it is experimental and not yet released. Neither is Chromium 66. The latest full release of Chromium (as used in Chrome Stable) is 65. Vivaldi 1.14 (Stable) is on Chromium 64, and Vivaldi 1.15 (Snapshots) are on Chromium 65. (So, by the way, is Opera Beta. Opera Stable is on Chromium 64). Behind the scenes, Vivaldi test version, always running ahead of Snapshots, is battling some regressions caused by the intake of Chromium 65. As soon as these are ironed out and publicly tested in the Snapshot stream, Then a new Vivaldi 1.15 Stable will be released on Chromium 65, and shortly thereafter Snapshot versions using Chromium 66 will be released. As a rule, we run somewhere between two and six weeks behind whatever version Chrome is using. It's necessary, because we have to fix everything a new Chromium intake breaks before we can release.
nickparkermusic last edited by
Thanks a lot for your posts. I get it now.
Steffie last edited by
This post is deleted!
opaq last edited by
Even though the thread got tagged as resolved, I just finished reading about chromium version numbers on wikipedia and it seems that chromium devs increase version numbers not for substantial new features but mainly just for... increasing version numbers.
@opaq This is true. They increment them according to a timeline, not according to feature progress. Just like a '56 Chevy Bel Air is different from a '55 Chevy Bel Air chiefly in its model year number. Vivaldi, on the other hand, will be increasing version whole numbers according to major feature changes. Like I don't know for sure, but I would think we will step from version 1.xx to version 2.xx when email is incorporated into the browser.