That actually makes the most sense. So similar to how Linux was started.

I think it was a general “when you leave Canada” policy.

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.

You can get the binary from the project’s website. Still not suggesting to f around with it.

If you have root you could theoretically add Memtest86+ to the boot order. There’s tools that allow adding boot entries in EFI. You could probably place a Memtest86+ binary in your EFI partition and register it with the EFI firmware. But I’m not suggesting to do it since you could make the machine unbootable and the problem might be on the storage path. I’m just thinking of should be possible.

Most machines I owned that had kernel panics had either an NVIDIA or an AMD GPU graphics adapter, along with bad memory.

FTFY

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.

As many have pointed out, price wise it’s not competitive. But more than that, the main feature of the Pi is its software support. I buy a Pi not because it’s got the top specs but because I know I can load a rock solid OS with security support and I won’t have to think about it. This is a problem for every Pi competitor.

On one hand I’d like it if the Democrats put up someone more certain to beat Trump. On the other Joe has shown he supports labor and things are moving in the right direction in that regard. I’d hate it if he we get a corpo Democrat that halts this progress.

Perhaps to people who are used to watching ad infested cable and don’t pay for ad-free streaming. So it’s not that ads aren’t detracting from the experience but that some folks are used to it. Getting those folks is growth. Number go up.

It isn’t? You might be looking at a different market.

If you were actually able to set it up via ssh,

I never said that.

I’m on Ubiquity’s payroll, definitely. I’m expecting a check in the mail any day now.

Oh for sure. I ran them without a controller for years. I only set it up to do a wireless bridge.

Perfect. This is consistent with what I was thinking and that Cloudflare’s changes won’t fix any recent bundles that might include malicious code.

For home, second hand Ubiquity might be. You can get flying saucers taken off from corpo upgrades for dirt cheap.

I was able to SSH into mine and I’m running their Docker container with a Unifi Controller instead of a cloud key.

I read the story and specifically the bit about the Github account. Isn’t this the Polyfill lib’s Github account? Because if that’s the case, how would a bundler solve the issue? The new owners could modify the original source, then the CICD jobs would happily publish that to registries and from there down into the bundles. Is it a different Github account they’re talking about?