←back to thread

The FORTH code for Chipwits is released in the game's 40th anniversary

(chipwits.com)
210 points JoeDaDude | 1 comments | 21 Nov 24 18:44 UTC | HN request time: 0.209s | source
Show context
tombert ◴[21 Nov 24 19:37 UTC] No.42207795[source]▶
Forth has been something I've wanted to learn for years now. It seems weird to me that for most stuff in old computers, you have the option of "assembly" if you want your program to be fast, and "BASIC" if you want your program to be slow, but Forth lingers along as the "medium speed" language, despite at least looking pretty high-level.
replies(7): >>42207863 #>>42207931 #>>42208026 #>>42209557 #>>42210559 #>>42213720 #>>42213966 #
zabzonk ◴[21 Nov 24 20:02 UTC] No.42208026[source]▶
Very fast (faster than naive assembler) but not at all high-level; having to look after the stack is a bit of a pain. Writing your own FORTH is fun - it doesn't need to be in assembler - I once wrote a FORTH-like scripting language in C++.
replies(3): >>42208089 #>>42212501 #>>42215623 #
1. Someone ◴[22 Nov 24 09:54 UTC] No.42212501[source]▶
> Very fast (faster than naive assembler)

Depends on how naive the assembler programmer is, and, I would think rarely, if ever, on modern hardware because the many subroutine calls kill branch prediction benefits. Also, on lots of old 8-bit hardware, defaulting to 16-bit integers will kill performance relative to native assembly in cases where 8-bit integers suffice.

(Of course, you can fairly easily replace hot loops by assembly or (more difficult) change the forth compiler to compile parts to native code, fuse words, etc)