4 ms·
Forth works quite well for problems that fit its stack-based model, but that's not every problem. For instance, having to manage and permute data on the stack
by zozbot234 5y ago
Forth works quite well for problems that fit its stack-based model, but that's not every problem. For instance, having to manage and permute data on the stack is often more awkward than doing the same things in languages that use ordinary variables. And working with only a single stack at a time, it's not clear how such languages might express parallelism, which is otherwise a very natural expectation for a functional language. Even things like complex data types, pattern matching etc. get needlessly awkward.
- codr7 5y agoIt's quite possible to add variables to Forth, which means you can pick the best tool. Keeping computations on the stack then feels similar to the push to keep computations out of the IO monad in Haskell.