If you want to solve computing problems more directly, you will want to apply the approaches of Thinking Forth, regardless of the language you use. A lot of sof

If you want to solve computing problems more directly, you will want to apply the approaches of Thinking Forth, regardless of the language you use. A lot of software and features are there to communicate with other people and their software. Forth is syntax for talking with the machine, and you can learn to distinguish between the two by engaging with Forth and trying to do more things with it. Forth is also a pretty good development target, if you need a "fully featured" stack VM with a repl. There's never been a requirement that using Forth means "writing the entire system in a Forth that you bootstrapped yourself". Sometimes you want to have a little build step on top, and sometimes you want to target a system that has more than the minimalistic or standards-driven stuff, or you want to have a small interpreter over library code that has implemented the fast algorithms already. Forth systems tend to be personalized, quirky, and under-documented, but most are also easy to strip down and examine closely.