2026-06-19 00:43:20 <cleobuline  > the place to be on the net https://labynet.
2026-06-19 00:43:36 <cleobuline  > the place to be on the net https://labynet.fr
2026-06-19 04:53:44 <oak         > I wanted to share this really cool literate programming style intro to writing a Forth: https://github.com/nornagon/jonesforth/
2026-06-19 04:54:19 <oak         > Last year I went through it and wrote my own based on it, but with C as the host system rather than x86 assembly: https://codeberg.org/kira/forth32/  It was very fun & challenging!
2026-06-19 10:22:31 <veltas      > oak: Might say in the README which file to start at if there's an order?
2026-06-19 10:25:03 <veltas      > Oh it's just the forth without the literate stuff?
2026-06-19 10:29:37 <veltas      > Glad you enjoyed it
2026-06-19 10:30:10 <veltas      > Have you written any applications/programs in Forth?
2026-06-19 15:18:24 <bjorkint0sh > veltas: the point of forth, like lisp, is to have been implemented, not programmed in ;-)
2026-06-19 15:19:24 <lofty       > my chess program may be an exception to that, although I think it's going to be a major benchmark for forth performance >.>
2026-06-19 15:21:19 <bjorkint0sh > such lofty ideals.
2026-06-19 15:21:25 <bjorkint0sh > great!
2026-06-19 15:21:49 <lofty       > style question: "condition if    x func    else    y func    then" vs "condition if    x    else    y    then func"
2026-06-19 15:30:03 <lofty       > bjorkint0sh: I realise that you are not supposed to write hot code in forth, but to discover it is hot code first it must be written :p
2026-06-19 15:30:23 <bjorkint0sh > naturally.
2026-06-19 15:30:40 <lofty       > ...not that it is clear to me how to profile Forth code.
2026-06-19 15:30:41 <bjorkint0sh > it's clay!
2026-06-19 15:32:15 <lofty       > (I also suspect this is probably going to have to be written for the lowest common denominator forth :p)
2026-06-19 19:47:05 <oak         > veltas: I haven't written anything substantial, no. I'm still learning.