FOSS also depends on them, many FOSS contributors are employed by proprietary companies.

OP is just talking about layout, not implementations.

Papers forked from Evince.

I love when I try to open a file and macOS tells me I can’t because can’t tell if it’s safe. There’s literally no way to open it from here.

You have to hit ok, then go so settings, scroll down to security, and hit a button to specify yes I actually want to open this file. It then reprompts you again but now with an open anyway button.

I love my MacBook’s hardware and battery life, but MacOS is such a letdown.

I don’t think that’s the case here. This is Lutris, a GTK3 app. There shouldn’t be any GTK changes breaking themes here. It seems like OP’s theme is just broken.

This is overly complicated. Just install Java then run

flatpak --user override --env="FLATPAK_ENABLE_SDK_EXT=openjdk" com.vscodium.codium

Note this works for all other SDKs too. It works especially well for programming languages like Rust that have their own package manager.

Doesn’t work so well for languages like C/C++ where you use your distro package manager to install dependencies. In those cases it’s easier to install VSCodium inside a container where you do have access to a distro package manager.

The kernel is a snap in Ubuntu Core, but you still need to reboot. I don’t think there’s a nice way to work around that.

Fedora IoT is similar to CoreOS, that seems primarily aimed towards Pis.

I haven’t watched the video yet, but keep in mind “resource usage” being lower isn’t always better.

For example, Plasma had an issue for some people where animations would not happen, freeze the system momentarily, and stutter. The reason why turned out that these people were using slow drives. Plasma was trying to load the bytecode for the QML animations from disk, but the IO operation took too long so the animation suffered. Had this bytecode been stored in memory, the performance would have been better.

But I also don’t want to discount the fact that some (perhaps most) of the time, high resource usage is a bad thing caused by poor programming and using technologies that are heavier, like Electron. Whether those tradeoffs are worth it are another matter.

I wish more developers actually used their software low-end devices to find performance issues. I recently got an Intel N100 and it’s actually been a decent experience on Linux, though Gnome shell’s animations are a bit stuttery even on Gnome 48. Haven’t tested any other desktop though.

@Zamundaaa@discuss.tchncs.de

It’s not making it worse. They like anime, so they have an anime girl as the mascot; a very tame one too.

But some people freak out about it.

If you use Anubis for free, he asks that you keep the girl on for marketing purposes.

If you pay / support the project, you can remove it.

Honestly, it’s a good way to encourage people to pay up because some people absolutely hate it.

I was wondering about that too. At first I assumed they were only allocated a few of the cores for their testing, but a typo seems more likely.

It’s actually pretty nice in some situations.

One thing that bites me about Loupe / Image Viewer is that it always goes through images in alphabetical order, despite the sort option you have set in nautilus.

Sushi does go through items using the same sort option set in nautilus.

Though it can be finicky with videos, so I don’t use it for that.

Good thing I use the Flatpak version of Sushi, I’ll just remove the network permission.

On some systems neofetch would actually run quite slow. Even on my fast system it would occasionally take a second because it hung on one step.

NixOS was troubleshoot central for me. Not all programs behaved as expected with Nix’s unique design.

I looked into this a bit more. It turns out that Metadata Cleaner was marked end of life by the owner because it’s no longer being maintained. This is different from the more common scenario where an app is using an end of life runtime. I guess Discover decides to remove apps that explicitly marked as end of life.

Still, it’s a poor UX to not give the user the choice. You may be able to work around the issue by pinning Metadata Cleaner, either using the CLI or Warehouse, an app to graphically manage flatpaks.

The authors found and reported vulnerabilities in Pagure and Open Build Service. These vulnerabilities have since been fixed.