Implementing a Forth is a great incremental process, all you need is a processor with stacks, registers, and RAM. Words are just lists of addresses. Once you have the base execution routines, e.g. DOCOL, NEXT etc., implementing the rest of the interpreter is easy. It can even be done on a calculator or in-game computer![1]
That's why it's important to choose simpler systems. I've been having fun writing a Forth-based Z80 operating system for the TI-84+ calculator[1]. There isn't too many moving parts and there are many "toy" systems to learn from such as one that boots up to a smiley face[2]. It's all about choice of architecture.
The beauty of Forth is that parsing is trivial, just read a space-delimited word from the input buffer and do a simple string lookup through a linked list. The syntax is whatever you want it to be. For me, I modeled my interpreter/compiler heavily off of the jonesforth implementation in x86 assembly.
I found out about Lisp a year before Forth! Working through SICP, watching the lectures and of course writing lots of Scheme programs have really helped me improve.
Emacs encourages this behavior because its operations that work on sentences require the use of two spaces after a period. Although it's possible to make it work with single spaces, it won't be able to reliably distinguish between abbreviations (such as etc.) and the ends of sentences.
A truly masterfully written article that makes us yearn for the days now past when everything, both inside and outside of ourselves, was much quieter.
The amount of noise today is unprecedented. I am reminded of the movie _Her_ in which one sees a world where technology can move into the background and augment human relationships. Granted, there are moments in that film when the tech hurts instead of hinders, but compare that to today's world where everything has the "in your face" mentality.
I'm surprised the Movfuscator hasn't been mentioned yet. It compiles C code into unconditional MOVs, and if you watch the author's Derbycon 2015 video there are ways you can scramble the MOV instructions, truely making it a decompilation nightmare.
[1] http://web.archive.org/web/20190516084513/http://mycpu.eu/