Well, if people would stop storing anything except than return addresses on the stack, yeah, probably even 32 KiB of stack would be enough for anyone. It'd also single-handedly stop all kinds of stack-smashing attacks, too: can't overwrite a return address on the stack if nothing stores data on the stack except the CALL/RET instructions.

Unfortunately, the current zeitgeist is still to have "writeable stacks" which are only moderately less horrible for the security than "executable stacks".

> For lex and yacc, that means the original .y and .l files. You don't have a choice if you want to be compliant with the terms.

Okay? I don't say "drop .y and .l files", I say "throw in the .h and .c produced from them as well into the tarball distribution".

> Also, shipping the .h and .c files in addition also ends up confusing the build systems of the time.

How?! If it were true, then merely having them in the source directory after running "make" for the first time would also break the build which obviously is not something that ever happened.

"Those take less space than lex/yacc so of course not".

    for (items, 0..) |item, item_index| {
        std.debug.print("{}", .{item});
    } then {
        std.debug.print(", ");
    }

My favourite example of troubled blind translation is still "naked conductor runs under the carriage".

The modern debate about whether LLMs are conscious are not has lots of people whose position is "no, they're not" but with arguments not that much better than Descartes (and also coming from the position of tradition). That's why I bring him up.

> Especially since there is a mountain of evidence proving he was wrong.

Only if you accept a particular way to interpret it. After all, I can show you an experimental proof that apparently the rays of cold (in addition to the rays of heat) exist; but that experiment can easily be re-explained in terms of infrared radiation only.

No, we don't. The humans claim that they do, but they may as well be philosophical zombies who claim to have such experiences without actually experiencing them (just as animals don't actually experience pain even if they behave as if they do).

    Block structure is traditionally considered an a priori requirement for algorithmic program-
    ming languages. Most new languages since Algol-60 have block structure. Reasons exist,
    however, to omit the general form of block structure — nested procedure definitions in which
    references to identifiers defined in outer procedures are permitted — from programming
    languages, especially those intended for systems programming applications. This paper
    reviews the concept of block structure and considers its advantages and disadvantages. It
    concludes that, in many cases, a module facility is superior to block structure and should be
    considered in lieu of block structure in future languages.

Well, yes, precisely. Just two verses earlier Samson prayed to God, asking to grant him a last bout of strength to take revenge at the Philistines for blinding him: "And Samson called unto the Lord, and said, O Lord God, remember me, I pray thee, and strengthen me, I pray thee, only this once, O God, that I may be at once avenged of the Philistines for my two eyes."

But those are the older translations — those quotes are from Luther Bible (1534) and Gdansk Bible (1632); you can find newer translations that use the wording of "let me perish with the Philistines" variety as well.

Which, as I understand, is pretty much the lesson that most of theologists derive form the story of Samson: don't let your lust blind you and make you stray from your duties to the God.