Here's what I'm hearing:
How would you design a Forth interpreter to encourage more people to solve actual problems with it? :)
How would you design a Forth interpreter to encourage more people to solve actual problems with it? :)
The issue as I see it, is that you have to have a model of the datastack in your head at all times. That's fine for your own code, but for other people's code, stack diagrams will only take you so far.
The ability to scan code, rather than reading it, allow you to mentally drill down when you are ready. Forth requires immersion.
Something like https://xorvoid.com/forsp.html I'm guessing is really the bridge. Something that allows variables without being too complex.