I only know two good FORTH programmers.
One is Chuck Moore. I met him once (he was doing chip design for Toshiba or something at the time). Interesting, smart guy.
The other one wrote a bunch of Finnegan’s control software (for their line of mass spectrometers). He was pragmatic about the language and its limitations.
Every single other use of FORTH that I have seen has been a disaster. The unfortunate fact is that the people attracted to this language seem to be the ones least able to write good solid code in it. Let’s see: Several disasterous attempts at video games at Atari, some early “hardware bringup” utilities (that didn’t catch some low-level timing problems because FORTH is nowhere close to native speed, despite what you might hear to the contrary), some other projects that I have mercifully forgotten.
With that said, I think that everyone should write a variant of FORTH at some point in their career; it’s simple to implement, and has some interesting and quite practical ideas for working in a primitive environment (e.g., “pages” instead of a complex file system, a ubiquitous built-in assembler, a scoping system that at first seems too simple to possibly work). It’s a slick system as long as you don’t try to misapply it. Writing your own version is an easy way to get it out of your system.
(I really will have a response to the “Why are we still using C” question. You’re not going to like it 🙂 )