The greatest Forth book is Forth on the Atari - Learning By Using by Winfried Hofacker. It’s an old book, published in 1983 in Germany, but the concepts it embodies are timeless. Available as a PDF http://www.atarimania.com/documents/FORTH-on-the-Atari-Learn... but I have an original copy :-)

If ever there was a time to say "Don't judge a book by its cover"...

Tl;dr:

> The Forth way of focusing on just the problem you need to solve seems to more or less require that the same person or a very tightly united group focus on all three of these things, and pick the right algorithms, the right computer architecture, the right language, the right word size, etc. I don't know how to make this work. My experience is, you try to compress the 3 absolutely necessary layers to 2, you get a disaster.

The other end is the conventional development method where each work in their own silos without a detailed idea of the others. This leads to bloated systems.

Precisely: https://plforums.org/practice/minimal-features-required-for-...

That comment dates from before I built this: https://github.com/akkartik/mu#readme