Why would anyone pick UTF-16LE? All the disadvantages of UTF-8, none of the advantages. The only reason to use it is when dealing with legacy systems that used it.

Code point order would be somewhat decent, but even better is to use the user’s chosen coallation order from their locale settings if possible.

The languages in a language menu should each be written in their own language. So German should be “Deutsch”, English should be “English”, Japanese should be “日本語”, etc.

Source is The Onion. There’s more than just the headline, and it’s a classic.

Music CDs or data? Music CDs have built-in error correction, data CDs don’t. You can certainly extend the lifetime if they’re stored in the dark in a cool, dry place (UV light, heat, and humidity all damage the dye that gets burned to encode them) but they’re not reliable archival storage without error correction.

They don’t last very long. About 5-10 years at most, and that’s if you bought special archival burnable DVDs. If you depend on them for backups, you should check the integrity annually (always include a checksum like SHA256 with any backup archive).

Sure, I should have gone further.

Systemd/GNU libc/GNU Coreutils/GNU BASH/Linux/X11//GTK/GNOME
Systemd/GNU libc/GNU Coreutils/GNU BASH/Linux/X11/GTK/LXDE
Systemd/GNU libc/GNU Coreutils/Zsh/Linux/X11/GTK/GNOME
Systemd/GNU libc/GNU Coreutils/Zsh/Linux/X11/GTK/LXDE
SysVInit/musl/Busybox/tcsh/Linux/csh
Systemd/GNU libc/GNU Coreutils/Zsh/Linux/Wayland/QT/KDE Plasma
Systemd/GNU libc/GNU Coreutils/Zsh/Linux/Wayland/QT/LXQT

etc, etc.

There are thousands of combinations of the possible layers needed to make an OS.

Systemd/GNU/Linux/GTK or Systemd/GNU/Linux/QT, really…