CBofN VS if-then-else

Source code for the second book:

https://github.com/gwf/CBofN

Use DieHard to avoid crashing newer window managers such as CWM:

https://github.com/emeryberger/DieHard

Check out stutter from the Computational Beauty of Nature too:

https://github.com/gwf/CBofN

cat data/demo.lisp | ./bin/stutter

Have a look on the file on how integers and aritmetics are implemented.

The books explains that, but is not free. But you can get it somewhere else.

From the The Computational Beauty of Nature:

https://github.com/gwf/CBofN

If you use CWM as your window manager, it might crash as some of the software only works fine

Read The Computational Beauty of Nature and compile the associated examples:

https://github.com/gwf/CBofN

On C, compilers in the 90's sucked up a bit, and the code wasn't much better.

Consider this:

https://github.com/gwf/CBofN

This code crashed CWM under OpenBSD 7.2, but it worked under FVWM.

https://mitpress.mit.edu/9780262561273/the-computational-bea... and

https://github.com/gwf/CBofN

On Debian/Ubuntu: install xorg-dev build-essentil git and clone it.

*BSD users: You and we already know what to do.

This is a really unique book, but it is quite dated as the graphics/simulations are written in C (https://github.com/gwf/CBofN). But I don't think the book text has any code in it nor does is it necessary to read the code to read the book. Rather it is mostly conceptual with some mathematics.

I agree that English as lingua franca of computing makes sense, especially when communicating with non-(German)-native speakers. But one important reason why German is no longer viable for this is the terrible state of translation from English to German. Instead of using the "established" German terms, English terms are usually translated 1:1 to German, usually by machine translation, or bad human translators who don't have a technological background.

And instead of this butchering of the fine German language, just switching to English is indeed the better alternative.

My favourite trivia is that the 'else' in 'if-else' is a bad translation from German into English btw ;) (https://github.com/e-n-f/if-then-else/blob/master/if-then-el...)

There is a neat history of the early syntax of conditional expressions here https://github.com/e-n-f/if-then-else/blob/master/if-then-el... titled “if-then-else had to be invented”. It seems “else” originated in Algol 60 as a hasty translation from German. The CPL project started in the early 1960s when it was not yet certain that Algol-style block structure and keywords would become the common basis of most programming languages.

If..then..else had to be invented

Not to mention that linux-pam's `[success=2 default=ignore]` isn't even standard, I think OpenPAM only has the five control flags required/requisite/sufficient/binding/optional. (One may reasonably despair as to the difference between "required" and "requisite".)

It's almost as if PAM were developed before the invention of the if-then-else construct in the 1950s.[0]

[0]: https://github.com/e-n-f/if-then-else/blob/master/if-then-el...