Basically the Matrix Spec Change Proposal system, I like it. Opens the floor to more players, gives tool authors a list of protocols they could choose to build on, and hopefully compositors will choose to adopt or adapt one of these protocols before writing their own.

I put newlines in my filenames to break both CLI tools and Windows filesystems

Taking courses which involve subjects that you will likely never encounter in the workforce is a thing in every discipline. Most engineers don’t need to manually solve differential equations in their day jobs, they just need to know that they exist and will often require numerical solutions.

Getting your hands dirty with the content provides a better understanding when dealing with higher level concepts.

zsh-syntax-highlighting

There’s also a fork called fast-syntax-highlighting, I use it.

Optional crash reporting was merged. Most of the backlash in the PR is about the significant dependencies (Google’s BreakPad) which were pulled in with it.

However, by default Audacity isn’t built with it, you need to specify a CMake with the URL to send data to. No distros that I know of enable reporting.

Judging purely on the dependencies I see in pacman, nsxiv depends on imlib2, which pulls in a lot of libraries, while imv links to a subset of those libraries directly.

What about adding the flags last?

rm deletethisrepo -rf

It’s probably the biggest deal for games running in xwayland

How is it compared to wofi?

If you say “a 10d10”, I know what you mean, but “10d10” is definitely the sum of 10 10-sided dice.

More people should be like you.

Exact same. Sway’s 1.0 release was March of 2019, and it did everything I needed.

Even playing games on my desktop, Xwayland worked fine for me.

8GB memory + two Firefox profiles makes things difficult on my laptop.

Others have mentioned disk usage and desktop integration. There is some truth to them, but shared runtimes keeps disk uasge down (although worse than native apps). Desktop launchers now search /var/lib/flatpak/exports/share/applications by default, but I’m still having issues with themes in one or two niche apps.

Trust is the big one. The benefit of your distro’s packages is that they are maintained by a limited number of maintainers. Flatpaks have a much, much larger number of maintainers, which is where sandboxing comes in. Flathub now marks apps with lax permissions as “potentially unsafe”, which is a huge step in communicating this to the average user.

Most desktop apps can get away with having next to no access, as long as they support the appropriate XDG desktop portals.

Ultimately, your mileage will vary, as there are many classes of application which are ill-suited to being sandboxed. Program launchers, programming languages, IDEs, file managers are a few.