Kitty can’t use bitmap fonts because of how it draws to screen & bitmap fonts don’t scale. You would need a different terminal for bitmap fonts or choose a different font.
While true & I remember folks actually using this in arguments for ‘slow development’, there is some merit to versioning differently for something expected to get minor updates to perpetually follow latest specs such. I can’t imagine trying to discern what a “breaking change” would be in this context. Or would you make a new version for every visual redesign? Dates might have just made more sense, but maybe ESR is easier to follow with the current scheme.
Most distros are running the same software. The biggest difference is your package manager & community. Personal preference is NixOS but that ain’t beginner-friendly even if the rollbacks from bad states would help. Arch isn’t as difficult to set up as it used to be & has been more stable than a lot of distros in my experience so I wouldn’t discount it but .pacnew files can bite you if modifying in /etc instead of in the home folder (when possible). Of the things folks normally suggest as a first go, Fedora would probably be my pick (not yet had a problem) as everything Ubuntu-based still rubs me wrong for support & leadership.
One advantage of linking a YouTube video in an aggregator setting is if the video goes viral, everyone is spamming Google’s server for delivery instead of hammering smaller services. Video is pretty expensive, so for now I see no issue abusing YouTube (assuming everyone here is already ad-blocking & DNS sinking anyhow).
It’s pretty hard to fight hegemony when your salary is just built on donations. A lot of important tech is also paid for via government grants then the private sector gets to use it and erect the walled gardens when it should be in the commons.
Authy requires a phone number last I checked & is a part of a for-profit entity. TOTP management is a simple task so there is no reason not to be using something open source.
It was usually recommended to lock to inputs anyhow with all the fetchers requiring a hash which I hated having to manually update & like the UX flakes provides (I really wish they supported more than Git & Mercurial tho). You can still have different evals tho if you point to latest.tar.zstd or other non-hashed thing like a branch where the referred to can change & it won’t reproduce. I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?
Saving the dependency is pretty big since each flake you import will bring along its jungle of dependencies now in your downstream project. I can’t think of a use case where < 10 lines is worth a dependency—especially since as you noted, lib has the glue right there for you to put it all together.