Yes! In fact, Chromium was originally a fork of WebKit, as WebKit was a fork of KHTML. In both cases the codebases have diverged quite significantly though.

The core of Safari (WebKit) is open source. If it weren’t they’d be violating the GPL license of KHTML.

Kubuntu, because it’s the most solid distro I’ve used that meets my needs.

They don’t really compete. Dark table does image processing, whereas Digikam’s major strength is its library organization.

Containers are great, but I find Docker’s way of making container images to be pretty bad, personally. Fortunately you can use other tools to create OCI images and then copy them into Docker, as the runtime is pretty nice for dev machines.

Yeah, adding a separate microarchitecture like amd64v3 would be a separate item. They might be able to do that with amd64v3 overlay repos that only contain packages that most benefit from the newer microarchitecture.

Personal stuff goes in ~/Projects

Work stuff goes in ~/Work/Code

Especially if you’re using raid5 for multi disk.

Still pretty important given how many systems are using the 1.0 series.

Snaps have had a permission system for at least 5 years now.

I don’t have a good comparison for this since my Intel CPUs are from 2014 or earlier, but I was thoroughly impressed with how well my new AMD laptop did video encoding (compared to the only-as-expected bumps in performance otherwise). Do you have examples of how much better QuickSync is than VCN?

You’re making my point for me though. Each of the other things you’ve suggested is more work than requires more expertise. Popping up an emulator on an existing box and dumping a ROM in there is something an intern can do.

All of these other things can be done, but they’re not as quick and simple, and that’s why we’re seeing this in the first case - Nintendo went with a quick and simple solution, and someone found a bug (it still plays Windows noises).

I take it you’ve never ported an application to a different platform running on a different hardware architecture before.

This looks a whole lot like it’s probably some random emulator they grabbed and full screened?

Making an FPGA for all of this is far more work than pulling an open source emulator and sticking it on a machine…

An FPGA seems like a lot of effort, but an SNES emulator running on a Raspberry Pi seems like it may have been a better option IMO.

Wayland was entirely unusable and mired in politics. (Still is mired in politics tbh.) So Canonical took the things they wanted, added things they needed to get it working, and called it Mir.

When Wayland finally became functional, they also made mir a Wayland compositor.

Some of the Wayland Frog protocols stuff is stuff that originated with Canonical trying to make Wayland usable before they took their ball and went home because the giants of the industry didn’t want to talk to a company of under 1000 people.

Much more appealing to me is running Android apps on Linux officially. I don’t want to use Android as my main system, but I sure as heck would love to have one or two Android apps available on my Linux Machines.

It’s not a perfect comparison, but if we go by the Steam Hardware Survey, the first item I can find on the list that’s not supported with the latest beta drivers is the GT 730, at 0.21% of users. And it’s from June 2014.

Its passmark score is 835, which is lower than the 9 year old Intel HD 520 (867). I somehow doubt though that driver support for Vulkan/Wayland will be the major blocker.

Don’t their current beta drivers support like… 10 year old products?

I have a lot of complaints about Nvidia (which is one of the reasons I moved away from their cards), but longevity of support hasn’t really been one of them.