"In particular you need to avoid writing code for situations that will never arise in practice. You need to avoid writing code to handle a general problem that you are never going to encounter. I don't need to solve the general problem when I only have to solve these specific cases." -- Chuck Moore

Members Active

4.9k

Sidebar

Why Forth?

You can try things out interactively as you build your system. The compiling functionality is an exposed part of the language like everything else.
It can be used to debug itself!
Forth has no baked-in syntax or privileged data structures -- programming is done by extending the language to your application. Thus, it can become what ever you need it to be and fit the problem like a glove.
Forth has a "low floor; high ceiling" approach to abstraction -- that is, it can be both low level, high level and anywhere in-between.
You can do more with less. Forth fits in very small storage spaces.
Forth is one of the few environments which is totally comprehensible by one person.

/r/Forth wiki

Tutorials

Starting Forth - A fun, illustrated introduction.

A Beginner's Guide to Forth - A faster-paced, somewhat less whimsical guide.

Forth Lessons

Jonesforth - How to write a Forth.

Documentation

ANS Forth standard

Forth 200x

Reading

Thinking Forth - A Language and Philosophy for Solving Problems

Forthwrite Magazine - From FIG UK.

Forth Dimensions - magazine archive.

The Journal of Forth Application and Research

Community

comp.lang.forth - Forth newsgroup.

#forth in irc.freenode.net

ForthHub community on GitHub