I've already done that---ANS Forth for the 6809 (https://github.com/spc476/ANS-Forth).

Advanced challenge: make it self-hosting.

Video where I demonstrate how I explore JONESFORTH using GDB:

https://youtu.be/giLsd-bik6A?si=Gwm3NJdUzyrmmopH

"if you know one forth, you know one forth"

So implement four of them, and you will know them all! First Forth with indirect threaded code, second Forth with direct threaded code, third Forth with subroutine threaded code, and the final fourth with token threaded code.

I thought this was going to be a pun on the word "fourth", disappointed when I got to "final".

I doubt you will want to code professionally in Forth unless you work on embedded, so the dialect you learn doesn't matter too much. But it is interesting to implement a small interpreter and play with it.

This is a strange article imo.

I was expecting to see FORTH in bare metal C or ASM.

There is a common myth about newbie programmers that FORTH is write-only and that you need to type everything in one line, without comments or function calls etc.

Writing forth is super easy especially if you have a stack machine at your disposal. For example when you are building your own virtual cpu/architecture with assembler and compiler.

It's more trivial than to understand any JavaScript framework lol

Research FORTH more guys - it doesn't need to be strange and hard :)

ps. Lisp SUCKS

/rant

I was with you 'till the last line. :P

IMO Lisp is harder to implement than Forth, and LESS readable, butt MAYBE i fell into the same trap as others with Forth. hahaha