• monkyyy (2/2) Sep 14 https://users.ece.cmu.edu/~koopman/stack_computers/index.html
• jmh530 (3/5) Sep 15 I'm probably not going to read that. Do you want to summarize
• monkyyy (19/25) Sep 15 "tacit programming is also possible on a hardware level"

monkyyy <crazymonkyyy gmail.com> writes:

https://users.ece.cmu.edu/~koopman/stack_computers/index.html

I liked the chapters I read

jmh530 <john.michael.hall gmail.com> writes:

On Tuesday, 15 September 2026 at 03:16:17 UTC, monkyyy wrote:
 https://users.ece.cmu.edu/~koopman/stack_computers/index.html

 I liked the chapters I read

I'm probably not going to read that. Do you want to summarize 
what the main takeaways are?

monkyyy <crazymonkyyy gmail.com> writes:

On Tuesday, 15 September 2026 at 14:44:20 UTC, jmh530 wrote:
 On Tuesday, 15 September 2026 at 03:16:17 UTC, monkyyy wrote:
 https://users.ece.cmu.edu/~koopman/stack_computers/index.html

 I liked the chapters I read

 I'm probably not going to read that. Do you want to summarize 
 what the main takeaways are?

"tacit programming is also possible on a hardware level"

The array programming extremists are the clearest on this: 
https://www.youtube.com/watch?v=E_88uuwhdi4

I of course disagree with them using symbols rather then these 
things we call words; perfering function chaining i.e. 
`range.map.filter.reduce`

0-operator stack machines also can just implicitly grab their 
arguments

---

roughly 4 sections to the book:

1. thoery, he defines a different way to talk about stack machines

2. machines of the ancient past(skipped this)

3. Comparing a 9-bit-opcode but like several operator 
machine(something in the 70's idk) with a 11-bit operator table 
but 0 address he makes lots of tables about how right he is 
saying you get such and such % of speed up, reduced transistor 
count etc. (very lightly skimmed this)

4. future design idea, proto data oriented design thinking