Incus is worth a look. It’s the fork of LXD, a container and vm orchestration/hypervisor program for cluster setups and infra models. Incus sits on top of the lower level LXC (Linux Containers).

• Incus Documentation: https://linuxcontainers.org/incus/docs/main/
• Incus Package Files: https://github.com/zabbly/incus#readme
• Incus Repository: https://github.com/lxc/incus#readme
• Incus Demo: https://linuxcontainers.org/incus/try-it/

Some nix language gotchas I’ve experienced while using NixOS personally:

1. Avoid with expressions unless with the inherit keyword for identifying hidden attributes in scope.
2. Avoid the rec keyword unless there’s tracking/control of infinite set recursion (self naming/references).
3. Avoid importing more than 1 instance of <nixpkgs> for any evaluation chain unless there’s magic compute and “infinite” memory.

Tricky is numero three, but crucial for fast feedback regardless of the current thing? I don’t poke around as much to know anymore but; legacy, flakes, community, and possibly others.

Two newer meta-ish search engines for encyclopedias (about 30+ wikis):

• https://encyclosearch.org/
• https://encycloreader.org/

The best CSS Framework? I don’t know. Complexity moves in mysterious ways. The many interpretations soc model must be satisfied.

1. CSS in CSS (canonical)
2. CSS in HTML (write once and time driven)
3. CSS in JavaScript (framework driven)
4. CSS in Shadow DOM (company/department driven)
5. CSS in Scoped Formats (IDE driven)
6. CSS in Preprocessors (design system driven)

I’d say, choices reflect environmental factors (social or otherwise) at play. If you’re lucky enough to choose, then suitability favors what draws the finish line closer? I’ve no advice since I’d rarely have the time/luxury to choose anyway. I’m usually thinking about the possibility of more types, sub–types (i.e in #1: bem, classless, etc), and the transposition strategy and speed between each class/type.