13 comments

[ 4.8 ms ] story [ 41.5 ms ] thread
Is this not more of a shell than an os?

Nevertheless an interesting idea. Unix pipes are basically concatenative, I've often thought how much mileage you could get out of going more in this direction.

Having said that. This has a lot of forth in it. (Dup, over, rot) I'm not sure the forth way, of passing options in the stack would necessarily work so well in a shell.

It kind of asks "What if we built an OS, but with all data sourced from immutable, append-only logs processed by pure functios?"

Probably not literally realizable right now, but IMHO, the closer we can get, the better

You could easily make CUNIX by starting with a log containing the state of a PDP11 at boot and a pure function which appends ignore previous input and the next PDP11 state to it.
> Unix pipes are basically concatenative, I've often thought how much mileage you could get out of going more in this direction.

You might enjoy the "Shell Has a Forth-like Quality" article. It's changed my shell scripting a lot.

https://www.oilshell.org/blog/2017/01/13.html

maybe I am dumb, but I don't really get how this is different to just piping between commands?
(comment deleted)
It's more than just a grammar. But specifically on that note, I'm assuming you know a POSIX Shell language. Spend some time with Forth and ask yourself if these are experientially the same thing.

Equifinality is extremely misleading.

Does this name come from reversing "CP/M"?
It does :) It's postfix commands(era, ren, etc..) except they work in postfix instead of infix.
Looks like the hardware this runs on has only 64 KB RAM.
Great work as usual.

I wish I were half as productive as Devine Lu Linvega. Perhaps I should get a sailboat and spend my time hacking without distraction, but I am not a fan of the seas.