I don't have recent experience with Forth, but traditionally, Forth didn't require such a "beefy" machine as a C programming environment.
For instance here's a fairly complete Forth environment in around 10 KBytes running on an 8-bit home computer. There was no C compiler at all for that machine, and if there would be, working with it would be a lot more hassle than a Forth REPL.
Aw, input is broken on mobile (Android + of course Chrome).
I'm getting a keyboard popup, and I appear to be typing somewhere offscreen (I can see a typing suggestion containing exactly what I've typed, which wouldn't happen if input wasn't going anywhere), but the text isn't appearing onscreen, then when I press Enter, I get an "OK" as though I'd hit Enter on a blank line... and the input I'd typed isn't cleared. So, "words <Enter> words <Enter>" shows "wordswords" in my keyboard's suggestion, and "OK\nOK\n" on the display.
Yeah no useful mobile support unfortunately. Plan is to replace the standard virtual keyboards (which don't have the necessary keys anyway) with a custom-rendered keyboard eventually.
For instance here's a fairly complete Forth environment in around 10 KBytes running on an 8-bit home computer. There was no C compiler at all for that machine, and if there would be, working with it would be a lot more hassle than a Forth REPL.
https://floooh.github.io/tiny8bit/z1013.html?type=z1013_64&f...
What's the appeal today, I don't know. But I'm in the "curly braces" camp. If I'd be a Lisp guy, Forth would probably be more appealing to me.