> Forth is quite "invidualistic", tailored to single persons or small
groups of programmers, mostly because it is natural and relatively
straightforward to implement a Forth system yourself (and you should)
and because the language is inherently malleable and adapts to your needs.
Therefore what I write is just one way of seeing Forth, which is both
a programming language and a engineering philosophy.
Sometimes... you don't need to understand anyone else, or to be understood by anyone else. Sometimes you just want to do what you need to do.
The goal of replicating understanding is all well and good, but that shouldn't be the primary goal of programming language development, nor should it be the primary goal of programming.
I don't think that anyone is suggesting that we start rebuilding enterprise service frameworks in Forth.
As a specific example, I'm dabbling in embedded programming (like Arduino) and switched to Teensy for the audio library. I guess the Forth philosophy would be to figure out how to program real-time audio from the microprocessor's datasheet? I'm not really a fan of C++ but I knew better than to go that deep.
Arduino itself is a good example of how a decent, common abstraction can help users get started.
Sometimes... you don't need to understand anyone else, or to be understood by anyone else. Sometimes you just want to do what you need to do.
The goal of replicating understanding is all well and good, but that shouldn't be the primary goal of programming language development, nor should it be the primary goal of programming.
I don't think that anyone is suggesting that we start rebuilding enterprise service frameworks in Forth.