https://youtu.be/5J3tYU_-IZI?si=t3B9d0Wtsvs26_i9

I think this is great. A lot of people want to have a free alternative. For me, the real value of this is the creation of a community and setting the foundation for something better than Mathematica. I'm on the side of those that think that programming languages are a tool of thought and Wolfram lang can be extremely expressive. I love non-mainstream but useful languages.

"And the Lord spake, saying, ''First shalt thou take out the Holy Pin. Then shalt thou count to three, no more, no less. Three shall be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, neither count thou two, excepting that thou then proceed to three. Five is right out. Once the number three, being the third number, be reached, then lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who, being naughty in My sight, shall snuff it.'

I guess nowadays it is much simpler to correlate some text with prior work, more so with LLMs. It is like those doping cases where several years later we are able to detect a previously unknown sustance in an old sample.

A. Ethics/Morals B. Power balance C. People are a valuable resource

I think we are all a little concerned it is C.

It's a grim thought and I'm optimistic, but the stakes are very high. Reminds me of Solaria (Foundation and Earth, Asimov).

Recently, reading the Wikipedia article about Z-order curves, I found this link inside the article:

https://hermanntropf.de/media/DBCode_mit_Erlaeuterung.txt

It's a blog post written in 2021, in txt, with ASCII diagrams and Pascal source code. I hope it warms your hearts.

A function executes, and some error happens:

- Return error value: try to handle the error ASAP. The closer to the error the more detailed the information. Higher probability of recovery. Explicit error code handling throughout the code. Example: maybe you try again in one millisecond because the error is a very low probability but possible event.

- Exception: managing errors requires a high-level overview of the program state. Example: no space left on device, inform the user. You gather the detailed information where the error happened. The information is passed as-is or augmented with more information as it bubbles up the stack until someone decides to take action. Pros: separate error handling and happy path code, cleaner code. Cons: separate error handling and happy path code, unhandled errors.

Worst case scenario: you program in C. You don't have exceptions. You are forbidden to use setjmp because rules. A lot of errors are exposed directly to the programmer because this is a low-level language. You return error codes. Rules force you to handle every possible return code. Your code gets incorporated as an appendix to the Necronomicon.