This really is an interesting article, and much of the introduction aligns with my experience: I love the concept, wish I had a reason to use Forth, but also I'

This really is an interesting article, and much of the introduction aligns with my experience: I love the concept, wish I had a reason to use Forth, but also I'm not and never have been a hardware person and haven't the foggiest clue what to do with it. For anyone who isn't familiar with the language, Thinking Forth[1] and Starting Forth[2] are (as far as I know) well-regarded books on the subject. [1]: http://thinking-forth.sourceforge.net http://thinking-forth.sourceforge.net [2]: https://www.forth.com/starting-forth/ https://www.forth.com/starting-forth/ Also, for anyone like me who dearly misses W. Richard Stevens, he wrote a Forth primer in the 70s. You can find it any several other documents on forth.org[3]. [3]: http://forth.org/tutorials.html http://forth.org/tutorials.html Previous discussions of this post over the years: https://news.ycombinator.com/item?id=3963896 https://news.ycombinator.com/item?id=3963896 https://news.ycombinator.com/item?id=8146306 https://news.ycombinator.com/item?id=8146306 https://news.ycombinator.com/item?id=8869150 https://news.ycombinator.com/item?id=8869150 https://news.ycombinator.com/item?id=21153555 https://news.ycombinator.com/item?id=21153555