it’s existential horror with absurd comedy elements. Pretty much the definition of “not for everyone”, so it’s not surprising some (most?) people strongly dislike it.

I have never met ADC fans outside of cons, and there they seemed very fun.

Inflammable is just likely to enflame confusion

:-)

cachyos is also topdog on distrowatch, by a wide margin

distro memes should be updated for 2026. i.e. with cachy,bazzite,steamos.

except RD it looks good.

For bluefast you could either take something with fast releases such as arch or fedora. Or something lightweight with faste boottimes, such as Peppermint or Bodhi.

iirc baseball was japans national sport before ww2

are you saying that japan was a US colony in 19th century?

there are plenty of good movies that are not reboots/sequel.

e.g. the top ten on letterboxd for 2026 contains 2 sequels and 1 reboot and 1 documentary/biography, so you get >50% original new movie stuff this year.

https://letterboxd.com/films/popular/year/2026/

how does it compare to other distros on the chart?

e.g. i can imagine that many military people us RHEL (which already is on the appropriate place on the chart).

vendors like Snapmaker

so far Snapmaker seems to have a good trackrecord, and has earned the trust of many, as their successful u1 kickstarter showed.

they promised to opensource large parts of their by end of next month. Lets see how that turns out https://support.snapmaker.com/hc/en-us/articles/33344279396759-Snapmaker-U1-FAQ#h_01K4VWF124M7HRBZEB4SS4EM09

that comes with support

biggest point.

When you build your own linux pc, you will always have a big risk of some unexpected problems. Lowering the bar of technical expertise to run linux is the main selling point here IMO.

Here are the steps:

• The attacker creates a standard Git repository.
• They commit a single symbolic link pointing to a sensitive target.
• Using the PutContents API, they write data to the symlink. The system follows the link and overwrites the target file outside the repository.
• By overwriting .git/config (specifically the sshCommand), the attacker can force the system to execute arbitrary commands–

amazing.

deleted by creator

i use nyarch btw

https://nyarchlinux.moe/

linux fork (not production ready yet) https://github.com/BrycensRanch/SnapX

tell your slicer to add bunny ears

e.g. https://wiki.bambulab.com/en/software/bambu-studio/brim-ears

the linux-file-deletion is used as a example for good software design. It has a very simple interface with little room for error while doing exactly what the caller intended.

In John Ousterhout’s “software design philosophy” a chapter is called “define errors out of existence”. In windows “delete” is defined as “the file is gone from the HDD”. So it must wait for all processes to release that file. In Linux “unlink” is defined as “the file can’t be accessed anymore”. So the file is gone from the filesystem immediately and existing file-handles from other processes will life on.

The trade-off here is: “more errors for the caller of delete” vs “more errors due to filehandles to dead files”. And as it turns out, the former creates issues for both developers and for users, while the later creates virtually no errors in practice.