This (well, with alt) has been a standard thing in x11 for decades. KDE kept it (with meta) when it added a Wayland backend to kwin.
The first desktop that I used on Linux was GNOME, probably either 2.0 or 2.2. It was a bit clunky, but it was fine. I distro hopped for a while and discovered Mandrake 9 and thought the desktop was great. This was when I discovered desktop environments. I hopped over to Fedora Core when it was first released and was unhappy with the desktop again.
So I started desktop hopping on Fedora. I tried XFCE, Fluxbox, Openbox, and several others. They were cool, and the KDE experience on Fedora Core 1 was not great. At some point I switched to Gentoo and used the KDE experience there. When Ubuntu came around, I found that while the install experience was good, the desktop was kinda clunky. I ended up sticking with Gentoo. When Kubuntu 5.04 came out, though, I switched over. And I’ve been using some combination of Kubuntu and KDE Neon ever since.
If GNOME had been my only option, I probably would have gone back to Windows. Initially because I found it clunky (and tbh kinda ugly), but more recently because every time I’ve used GNOME in the last decade or so, it feels like it’s lost features I used heavily. Meanwhile KDE has taken a different approach to configurability of trying to cut down configuration options by figuring out what a better option that everyone can agree on looks like. It’s still very configurable, but it has nowhere near as many knobs as it had in the KDE 3.5 days. You know what, though? I cannot think of a single lost configuration option in Plasma that I miss.
So I am strongly in the KDE Korner between these two, and much more weakly favour KDE Plasma vs. other desktops.
Not sure why you specify binary-based OS’s. Following Gentoo’s upgrade guide also gets you potentially whatever they want on your systemp
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.
Many US states got their capital chosen because when the territory became a state it happened to be the closest to the centre of population of the state. Jefferson City, MO is a good example of this. The three major population centres at the time were St. Louis, Kansas City and (to a much lesser extent) Joplin. So Jefferson City was right by the centre of population.
Meanwhile, most European capitals (including at the provincial level - think German states or French regions) came to their state by being the capitals and cultural centres of feudal states, which gives them more depth.
I don’t mean any offense to Iowa (this time), but there’s not a huge amount going on there. It exists almost exclusively as an administrative division.
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?
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.
They officially publish the snap, the flatpak and a deb in an apt repo.