> At the time, we found that the Chromium engine was secure and the most widely used – that was important to us. Moreover, Chromium was becoming the de facto web standard meaning that if we wanted web pages to not break, we’d have to fork Chromium.
I'll also observe that they made this decision around or before the time that Mozilla started oxidizing Firefox. So at the time, there was a lot of code churn, into an at-the-time unproven language, and the benefits had not materialized yet. If they were to start over now instead of then, the decision might be different.
https://vivaldi.com/blog/vivaldi-browser-vs-google-chrome/
> At the time, we found that the Chromium engine was secure and the most widely used – that was important to us. Moreover, Chromium was becoming the de facto web standard meaning that if we wanted web pages to not break, we’d have to fork Chromium.
I'll also observe that they made this decision around or before the time that Mozilla started oxidizing Firefox. So at the time, there was a lot of code churn, into an at-the-time unproven language, and the benefits had not materialized yet. If they were to start over now instead of then, the decision might be different.