Even for a Forth, 3KB of RAM is rather tight. Dusk OS intentionally de-prioritize compactness and it couldn't run on that amount of RAM. It can get a C compiler loaded in about 100KB of RAM, but 3? not enough to boot.

▲

tlavoie a day ago | parent [-]

OK, so we'd play with zForth then, as BogdanTheGeek notes here. That reminds me, I have a Scamp board sitting here on my desk that I really should play with more. https://udamonic.com/what-is-a-scamp.html

▲

vdupras 20 hours ago | parent [-]

"we'd", you mean in a collapse scenario? Forths are, by nature, "collapse-friendly", but one particularity with Collapse OS and Dusk OS is that they are fully self-hosted. This includes the tools necessary to improve upon themselves.

From a quick glance, it looks like BogdanTheGeek's Forth is written in C, which means that it's not self-hosted. If all you have is that disposable vape with this Forth in it, you lack the tools to deploy it on another machine or to improve it in place.

One could also port Collapse OS to ARM. I guess it wouldn't be a very big effort.

	▲	tlavoie 20 hours ago \| parent [-]
		Good points! Really, I should start with learning Forth on the devices I have first, before getting to concerned about others. ARM does seem like a useful target though, given that they're basically everywhere these days.