@amuletofyendor this demo is so cool! Is #durexforth referring to https://www.c64-wiki.com/wiki/DurexForth ?

@maxdevjs Yes, that's right. It's actively developed and complies with the Forth 2012 standard.

@amuletofyendor interesting... further curiosity: is it generally run in an emulator or actual hardware?

@maxdevjs It can run on either real or emulated hardware. I find it convenient to run in an emulator as you can paste code in from the likes of vscode. I'm sure it's personal preference though.
DurexForth provides both a cartridge and a disk image. Some additional libraries are only on the disk image, so I like to have both the cartridge and the disk images attached in Vice emulator.
Programs can also be saved to self contained files for distribution so the user doesn't need to know about Forth

@maxdevjs The usefulness of having both attached is simply that you can avoid typing load"*",8,1 every time you reset the computer, and the resulting wait for Forth to load, but you can still access the optional modules from the disk if you need them (I save my own programs to this disk too, while I'm learning).

@maxdevjs The manual contains details of saving a self-contained program. Essentially you can save the entire Forth runtime including your own newly defined words to a new disk. Further to this, you can define a word to run automatically after loading, and further to this, there is the "Turnkey" module for stripping out everything you wouldn't need in a distributed program, such as the interpreter.