Lots of people, myself included, implement a Forth without really using it. That makes it sound like a toy, but it's more like an important lesson in programming concisely and choosing a comfortable level of abstraction for the problem. Forth is designed to be simple to implement and extend, and that's the foundation of Forth as a whole philosophy: choosing a specification that actually solves the problem without generalizing or over-architecting the solution. Forth, the language, is just the set of tradeoffs that Moore thought was best suited to that, a position that most of the industry implicitly disagrees with(because they do things like introduce large libraries and dependencies where Moore is very DIY). It's a very concise language with a lot of sharp edges.
Look up "Thinking Forth" for more in this vein.