I must not be living in your universe then. The last time I experienced Forth was an interpreter on a cart I bought for my C64 back in the 80's. I think I popped it in the slot once, then it sat on a shelf for the next 10 years and finally got round filed. I can't think of anyone I know who would consider Forth more than a curiosity and more than one of them would try to re-write the module in Python, probably.
Alright, whippersnappers, listen up.
FORTH was incredibly useful in the day when many SS-50 Bus systems had 32KB memory cards. I had one that also came with an old 8-KB memory card, but wasn't functional because it's address space overlapped the 32KB card. A simple lookup of the address pins on the memory controller address chip provided the knowledge to re-address the card to a new range, and so I had a system with 56KB addressable memory (the processor card had RAM and ROM onboard.)
So what to do with the extra space? (Re-)Write my own FORTH based OS, which I had gotten from the FORTH magazine. The FORTH code was written in 8086 based assembler, but I had a MC6809, so a rewrite really sped things up. I even figured out how to thread the stacks so as to not have them collide, or simply scribble over all of memory.
As you can probably guess, the project was useful as a learning tool, not for any real work, but it was three years before the Apple or the IBM PC. I then wrote in Assembler (Flex, AFAIR) a printer driver to properly run my DEC LA36 in HiRes mode. I printed my first resume on it. A friend said "Don't use the bold font, it's ugly." My reply was that it was a testament to my skill, because none of the existing drivers outside of DEC equipment could do that.
BTW, SUN; IBM POWER; and OpenBOOT (AKA OpenFirmware) machines all used FORTH for boot loaders and console monitors. So it is more than a curiousity.
NOW get off my lawn. Or make my day, punk