03:03:59
##forth
<KipIngram>
Could be. Here's the spot:
03:04:24
##forth
<KipIngram>
OH - I get it now.
03:04:27
##forth
<KipIngram>
Duh.
03:04:37
##forth
<KipIngram>
All he's saying is that all computers have a return stack.
03:05:45
##forth
<KipIngram>
Ok, I'm pleading it was early and I'd had inadequate caffeine.
03:08:11
##forth
<xentrac>
oh, yes, he's saying that even non-Forth computers have a return stack
03:08:23
##forth
<xentrac>
which isn't really true and he knows it, but it's close enough
03:09:05
##forth
<xentrac>
I mean PDP-8s and MIX don't
03:10:16
##forth
<xentrac>
but when was the last time you had to debug a PDP-8 program?
03:12:54
##forth
<KipIngram>
Yeah, I always found it interesting that they got along for a while without them.
03:24:35
##forth
<vms14>
what if they really have a common return stack and he provides some sort of multitasking feature?
03:24:49
##forth
<vms14>
would be hard though
03:25:01
##forth
<vms14>
i wonder if there is any benefit
03:25:09
##forth
<vms14>
well space
03:26:24
##forth
<vms14>
also do not they run in parallel?
03:26:43
##forth
<vms14>
then it would not make sense
03:28:01
##forth
<vms14>
ah, didn't read the last stuff you said KipIngram
03:36:58
##forth
<xentrac>
KipIngram: subroutines were apparently invented before the first stored-program computer was working
03:37:44
##forth
<xentrac>
Mauchly's notes on preparing programs for the soon-expected IAS machine describe not just subroutines but also subroutine *libraries*
03:41:18
##forth
<xentrac>
but at the time I think the ability of the stored-program computer to modify its code was seen as affording important simplifications in the machine design through self-modifying code
04:05:49
##forth
<xentrac>
a thing I notice in this Strange Loop video is that Chuck's screen editor seems to be displaying the block number on the screen in large text
04:09:20
##forth
<xentrac>
I also didn't realize there was a memory-mapped address for each subset of the four communication ports, so you can jump to "all four ports at the same time" (15'53")
04:13:40
##forth
<xentrac>
I feel like maybe the two big missteps in these cores was to devote too little of them to memory and to not include a multiplier
04:22:22
##forth
<xentrac>
those are the specific things that make it uncompetitive with FPGAs in FPGA applications
04:22:40
##forth
<xentrac>
I mean also you can't program it in Verilog or VHDL or C or C++ but that's probably less critical
04:55:51
##forth
<KipIngram>
Man, I really just don't get the infatuation with functional programming. The world is not stateless and immutable. It's just FULL of things that change, and when we act in the world we DO THINGS TO STUFF. Trying to model a stateful, changing world with stateless, immutable software models just makes no sense to me.
04:57:43
##forth
<KipIngram>
The limited memory in the GA-144 really does completely change how you have to think about programming them, I think. It's like you're programming simple "logic gate like things," and you wire them up in a "circuit." I think it's more like designing hardware than software.
15:24:57
##forth
<crc>
forth.chat & my other servers will be down briefly while I upgrade the FreeBSD install
15:48:32
##forth
<crc>
maintenance is complete
16:03:58
##forth
<xentrac>
congratulations