Ignore the noise and use Ubuntu LTS. Subscribe for the free Ubuntu Pro service. This is something you do not get on Debian. Enjoy boring, trouble-free operation.
If you're hell bent on not using Ubuntu, use Debian. Enjoy boring, trouble-free operation.
In either case, use Docker. I don't know what the version of Docker is in Debian but in Ubuntu 22.04 LTS, it's recent enough so you don't have to f around with third party repos.
Not sure why this is down voted. This is exactly what happened. Trudeau ran on electoral reform in 2015. That was gonna be the last FPTP election, he said. Then they did some consultations with the public and said that not enough people wanted it. Shortly after, they threw the whole thing down the garbage chute.
I see this parroted now and then. Often the people I've heard it from are the type of folks who would drastically underestimate the complexity and effort needed to make things. I've also seen and worked on codebases made by such folks and usually it ain't pretty, or maintainable, or extensible, or secure, or [insert fav cut corners here].
Recall, to VAG's major shareholders, it doesn't matter where a VW is made since they would always collect and distribute the profit from its sale. To auto workers and their local communities on the other hand, it makes dramatic difference whether the VWs on their streets were made close by, or a continent away.
I guess Chromium isn't fully BSD. This could be the reason. Although I'd think reimplementing the non-BSD bits in Chromium would be less work than reimplementing all the bits, including the BSD ones.
Why are open source software monocultures bad? The vast majority of non-Windows OSes are Linux based. Teams who don't like certain decisions of the mainline Linux team maintain their forks with the needed changes.
Manifest V3 is a great example of this. You can only backport for so long, especially when upstream is being adversarial to your changes. We need an unaffiliated engine that corrects the mistakes we made with KHTML/Webkit.
And we could get a functional one today by forking Chromium and never accepting a single upstream patch thereafter. I find it really hard to believe that starting a browser engine from scratch would require less labor. This is why I'm looking for an alternative motive. Someone mentioned licensing.
Perhaps some folks just want to do more work to write a new browser engine. After all Linus did just that, instead of forking the BSD kernel.
Any intuition on why we'd expect opening the same page on a newly implemented browser engine that implements all equivalent standards and functions will consume less resources?
I do not understand the urge to start from scratch instead of forking an existing, mature codebase. This is typically a rookie instinct, but they aren't rookie so there's perhaps an alternative motive of some sort.
Even as far back as 2010 the corpo I worked for had an official travel protocol that dictated backing up Blackberries, factory resetting them, crossing the border, then restoring them from the cloud. That was for crossing any border.
