– Not getting as much outside contributions compared as e.g. – The hard deadlines on a 4 weeks release schedule(!) being too inflexible. – Them trying to cram too many features into new milestones. – Relying too heavily on telemetry – telemetry sometimes doesn’t cover the wider scope of why e.g. – Inadequate quality assurance, relying too heavily on machine testing. We could theorize on why their releases tend to have beta quality these days, some causes could be: Mozilla is fully in control of the development effort including engine development, they have no excuses. Because Vivaldi adds rather major modifications to Chromium compared to Chrome, Edge, Brave etc., it is more prone to breakage, as a result of them having to use Google’s code while also wanting to maintain their ambitious UI effort. Vivaldi’s UI is a special layer on top of Chromium which seems to break with every single new major release of Chromium, and they have to fix the breakage causes in time as to not fall behind. It can still happen occasionally, but with Mozilla, it happens all the time.Ĭompare this to how Chromium is being released: Major release, later 1 – 2 security updates for that major release, then next major release. Why? Because you can expect an emergency fix within days after each major release… Emergency fixes are only rolled out when a problem is both obvious and fairly widespread, and such problems are usually caught in the beta phase. Think the way Mozilla manages releases is indeed indicative of my “their stable is actually their beta” theory.

Firefox super slow and freezing