Now there are 3 competing standards Edit: 6ish accually

Turing Complete Configuration

• more extensible
• tend to be heavier
• harder to provide detailed error messages
• more difficult for new users

Data Based Configuration

• easier to use
• easier to provide documentation
• lighter to embed
• more limited usecases

To enable the use of flakes, you have to use the 'extra-expiremental-features flakes' flag.

Edit: Apparently they are called 'extra-expiremental-features' not 'extra-unstable-features'. Regardless the nix docs explicitly describe them as unstable here

https://nixos.org/manual/nix/unstable/contributing/experimental-features.html

Nixos

Pros

• Delarative Config
• largest package repos

Cons

• poor documentation
• cli and package management is in limbo with unstable flakes/cli

Yes, via termux.

I just use ffmpeg

In most cases you don't want one. It can make forks confusing and lend malicious actors more credibility than they deserve.

Copyright controls the code. Trademarks are the recognisable names/icons that identify a project.

I like curl's standard and trasparent release cycle. The consistent feature freeze before releases seems like a good idea to prevent bugs.

I'd consider dual-booting(windows+linux or linux+linux) or just installing a desktop environment. You can login to your wm and they can login to a full de

Congratulations and welcome. I use arch, btw

I use a shared boot partition all the time. I mount my EFI system partion on /efi. Then I bind mount /efi/$OSNAME to /boot in my fstab. Then I just manage my bootloader (typically systemd-boot or refind) manually. Any distros I install are installed in my encrypted btrfs partition within their respected subvolumes