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/

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.

Mathematical Markup Language (MathML)? I’ve thought about LaTeX/TeX strategies on the web for a bit ever since someone asked years ago about different approaches. I never got to poking around on my blog, but since then the masters have delivered unto us;

1. MathML (XML based web specification)
2. KaTeX
3. MathJax

In format conversion land we’ve been given; LaTeXML, make4ht, texmath, temml, and Pandoc.

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.

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 :)

I know of four PHP static site generators.

1. Jigsaw: Laravel Blade templates. Source Code
2. Couscous: Twig templates. Source Code
3. Sculpin: Twig templates. Source Code
4. Spress: Twig templates. Source Code

The key advantage is obvious: dynamicity “technically” comes for free. Feedback/debugging loops “can” be made instantaneous, and scaling to a large output is probably not too difficult.

One downside is that corporate minded developers and consumers online will think you’re a noob for choosing PHP.

The space of software hosting forges is sizeable. Most techy people know about GitHub and GitLab but many software forges exist (if considering the entire world). Here’s a few of note.

1. NotABug: Based on Gogs.
2. SourceHut: Suite of free software development tools built from the ground up.
3. Codeberg: Based on Gitea.
4. SourceForge: Mainstream software hosting.
5. Radicle: Decentralized on the service layer (discussions/issues). Git itself is distributed and decentralized.
6. Savannah: Suite of software development tools from GNU.