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.

Ho, some of us think alike. I stumbled onto this site while looking up related unshare namespace configuration. I do something similar.

After perusing the web dev blog feeds (finally).. it seems that there’s a “mainstream” coordination away from the client side;

• https://intercoolerjs.org/
• https://unpoly.com/
• https://htmx.org/
• https://turbo.hotwired.dev/handbook/introduction

Time until a transition to ‘json over the wire’? These are very handy libraries btw — I tried htmx previously.

..if it wasn’t for this guy visiting my country. I am now “enlightened”. Spoiler: Blockchain protocols computationally formalize/describe a government’s high power restraints within democracy. In civics (social studies), democracy is decentralized power (no/many kings) and therefore implicitly inefficient.

Democratic governments (in perfect world) communicate/act/bank;

1. In public (freedom of information)
2. With immutability (no deleting things)
3. With consensus (majority vote)
4. With inefficiency (to weaken bad actors)

Citizens and other low power (centralized) entities can do some of the above (federation), but mostly (wisely) communicate/act/bank;

5. In private (freedom of association)
6. With mutability (to protect privacy)
7. Without consensus (freedom of expression)
8. With efficiency (to build–up fast actors)

Individually, (5-8 > 1-4) no? But (1-4 > 5-8) in dictatorships (5-8)? Blockchain governments for maximal oversight? Not happening :)