> It's the same class of bug as manually parsing HTML with regex, it works right up until it doesn't

I'm sure you already know this one, but for anyone else reading this I can share my favourite StackOverflow answer of all time: https://stackoverflow.com/a/1732454

> Ringfencing laws post 2008 have made customer deposits in the UK very difficult to invest profitably, to the point where (at least last time I cared about this) they were charging commercial customers to have UK domiciled accounts.

I don't follow; why would regulations on consumer accounts change the price of commercial customer accounts?

As long as they keep other people’s money, they make money on it.

I was just thinking the other day about how AI will pretty soon be able to create this kind of explainers on everything quite quickly.

Amazing times!

Back before written deeds and the county clerk keeping track of land ownership, it was handled by memory. So they would have a young boy witness the land transfer, on the theory that if there was a dispute 30 or 40 years into the future, he could testify that the transfer happened. And to help him remember, they would nail him in the 'nads. Point being, dudes getting nailed in the 'nads has a rich historical tradition that pre-dates writing.

W11 is the best OS I've ever used, but everyone seems to hate it because Microsoft is so adamant in destroying its reputation by pushing Copilot and bugs instead of focusing on reliability. It's a shame.

At the risk of telling you what you already know and/or did not mean to say: not everything can be a value. If everything is a value then no computation (reduction) is possible. Why? Because computation stops at values. This is traditional programming language/lambda calculus nomenclature and dogma. See Plotkin's classic work on PCF (~ 1975) for instance; Winskel's semantics text (~ 1990) is more approachable.

Things of course become a lot more fun with concurrency.

Now if you want a language where all the data thingies are immutable values and effects are somewhat tamed but types aren't too fancy etc. try looking at Milner's classic Standard ML (late 1970s, effectively frozen in 1997). It has all you dream of and more.

In any case keep having fun and don't get too bogged in syntax.

> Layer 3: Paid, subscription-based search

Should actually be - Layer 3: Paid, ad-free, subscription-based search. (It's a subtle omission that indicates the direction Kagi search will eventually take).