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.

I don’t particularly write for an online audience, but netsurfers I speak a truth; short » long!

Yeah, obviously (duh), but the average estimated attention span online clocks in just under a goldfish (9 seconds) or maybe more!

I’ve only fully realized this by happenstance in a sorta offline–ish short/long blog experiment, but it blows my mind because my ability to focus is typically 2~4 hours.

I caught a glimpse of an interesting thing by chance. Meta Platforms aka Facebook hid the x from their login prompt on public pages–including government pages, then brought it back. ‘Twas on the desktop before mobile and perhaps (who knows) for a subset (as a test). A “login only public page” is for a near–distant future, set. Seriously though; developer documentation will become my final excuse to visit Facebook.

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

One of the best pizza making forums on the net is still;
https://www.pizzamaking.com

A lot of clothes dryers/tumblers have cheap threaded blower wheels that screw onto a motor shaft. Often, the wheel’s threads are stripped from constant thermal expansion.

When hot enough (it’s delayed), there’ll be a loud noise of metal spinning inside metal. The motor could be dying too (running hotter than normal) since it has the stronger threads.

One temporary fix involves wrapping copper wire around the motor’s threads for friction… at least while trying to think of a more “permanent solution” that does not involve buying/hoarding perfectly shaped blower wheels indefinitely.

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.

So, the other day I learned that the cool lingo is coins. I’ve rummaged through the depths for a bit and came across the most plain and straightforward breakdown of the cryptocurrency ecosystem ever written. Impossible! Most everything else is like deciphering a marketing slate.

The analysis on economies of scale within peer–to–peer networks and this answer on merkle trees vs blockchains are worth the read too.

So as you may know we have, knowledge.. or in the old black books of web witchcraft; the checkbox hack. I wonder though; did anyone ever go the final mile and create a kinda generalized “progressive polyfill” to fix the semantics of this so called hack?

Tangentially, a query for a details/summary polyfill brings up either rstacruz/details-polyfill or chemerisuk/better-details-polyfill with demo. Interesting.

It’s hard to “peek into” other knowledge domains successfully. The reason; marketing fuzz.

TL;DR: Blockchain data–structure is designed only for Bitcoin’s rules. Large deviations from Bitcoin go nowhere. Ethereum appears to be the only protocol with minor deviations from Bitcoin.