On the other hand:

• Loop-device exhaustion (slow, though Ubuntu has increased the limit via a patch).
• A single point of failure due to Canonical’s repository imposition (a closed garden).
• Unmaintained branches and snapped apps.
• Implicit installation of snapped apps through the apt CLI instead of the originally supported packages 🤬 (what the hell, Canonical!? Are you doing the same crap as Microsoft?).

The server-side closed garden is the opposite of an open ecosystem and the open-source community. You can add custom repositories to APT or Flatpak. Every new snap interaction feels like another step toward forcing the user to use it, instead of offering cool features that convince users on their own merits.

The last change (installing snapped apps when you run apt install) was horrendous. What’s next? Installing snapped apps when the user runs flatpak install?

Click-bait title. 👎 It’s a plugin for KWin. Here is the Pull Request, includes a video: https://github.com/taj-ny/kwin-effects-forceblur/pull/235

localhost

• Factorio (currently best management)
• Satisfactory (cozy Factorio)
• Captain of Industry (try this one)

Maybe this functionality was replaced by the next thing?

Automatic root filesystem soft-reboot: systemctl automatically reboots into a new root filesystem located at /run/nextroot/.

Developed by Saber Interactive. Caution.

I didn’t try yet: https://www.cmcrossroads.com/article/gnu-make-escaping-walk-wild-side

colon := :
$(colon) := :
url := https$(:)//something

I didn’t try yet: https://www.cmcrossroads.com/article/gnu-make-escaping-walk-wild-side

colon := :
$(colon) := :
url := https$(:)//something

A full price release for the first milestone, and because it is a Kickstarter, without any guarantee. I’m sure that the Patapon fans will be happy, at least.

deleted by creator

syscall -> asm -> page_fault

This a native machine code execution that crashed in your system. Could be an instruction that your CPU doesn’t understand (because the instruction is newer than your CPU, example: AVX512), or because your hardware returns an error when this instruction is executed (RAM issues?). Too difficult for me to understand this ASM crash.