Nick Nelson: Resource embedding in Forth	|How we put icons, images, UI definitions, CSS styling sheets etc. into our Forth executables.
Howerd Oakford: colorForth tokens	|News from colorForth
Ulrich Hoffmann: Enums in Forth	|How can we define Enums in Forth? Let's look at best practice and alternatives.
M. Anton Ertl: Are locals inevitably slow?	|Code quality of locals on two code examples on various systems
Bob Armstrong: CoSy NoteComuting environment demo	|Brief demo of CoSy environment which I use every day as a timestamped diary/log & to doing my accounting and mail_list handling .<br>CoSy is a Vocabulary in open Forth implementing reference counted dynamic lists very much modeled on Arthur Whitney's K , evolved from Ken Iverson's APL . Indexing is Modulo.
Nate Morse: Joy to the Web: A Zero Install version of Joy (not a production) Language called Pounce	|l could not get the "Joy language" to run on my hardware, so I started making interpreters (as one does). In the process of making interpreters, choices are made that deviated from "pure" Joy. I love the Forth way, and I am enamored by functional programming, so I followed Joy, Cat, Kitten, which lead me to make this browser based language, Pounce. Pounce has zero state outside of the stack and the program queue (dequeue), see<br>https://pounce-lang-show-case.netlify.app/<br>and<br>https://github.com/pounce-lang
Stephen Pelc & Gerald Wodni: VFX Future / more TUI	|Wodni & Pelc is already up & running, VFX is receiving new TUI tools
Leon Wagner: Tracking celestial bodies with a satellite antenna	|We added celestial body tracking to our fast antenna controllers last year, primarily for tracking the moon. During testing, we strapped a webcam to an antenna mount and tracked the moon from rise to set in the sky over Fresno, California. I'll show the time-lapse video of this.
Ulrich Hoffmann: Standard Report	|What has been discussed in the just past standard's meeting?
Klaus Schleisiek: uCore progress	|byte addressing and complete division/multiplication test
Bernd Paysan: Gforth 1.0	|Gforth is getting closer and closer to the 1.0 release; time to report what changes.
Klaus Schleisiek: German Academia and Forth	|A report on the 38th Workshop der GI-Fachgruppe "Programmiersprachen und Rechenkonzepte"
Glyn Faulkner: Tales from the Left-Hand Path: Dark Confessions of a Forth Hobbyist	|Question: What happens when you combine an unhealthy Forth obsession with a background in programming language implementation and a perverse liking for the GNU assembler?<br>Answer: Nothing good or wholesome...<br><br>Github for most mentioned systems: https://github.com/boxoffoxes
Andrew Read: Can I do this in Forth?	|A modern instrumentation control and data analysis application is astroimaging at amateur and semiprofessional observatories. A case for Forth software raises interesting questions!
Krishna Myneni: Progress Towards Porting EISPACK to Forth	|I will give an update on my status of porting EISPACK, the old Fortran package for obtaining numerical solutions of eigensystems problems, to standard Forth. I will describe the rationale behind porting this particular package, instead of a modern package like LAPACK, give an overview of the library modules present in EISPACK, and talk about some of the challenges in porting unstructured Fortran 77 code to current Forth and in testing both the original and ported code. Examples of use in Forth will be presented, for those modules which have already been ported.
M. Anton Ertl: Memory Safety Without Tagging nor Static Type Checking	|A significant proportion of vulnerabilities are due to memory accesses<br>(typically in C code) that memory-safe languages like Java prevent.<br>This talk discusses a new approach to modifying Forth for<br>memory-safety: Eliminate addresses from the data stack; instead, put<br>object references on a separate object stack and use<br>value-flavoured words. This approach avoids the complexity of<br>static type checking (used in, e.g., Java and Factor), and also avoids<br>the performance overhead of dynamic type checking for non-memory<br>operations.
Ulrich Hoffmann - Fuzzying Forth	|Fuzzing is an automatic testing strategy that can be used to increase the reliability of applications.<br>Application interfaces are tested with selected random (fuzzed) arguments in order to uncover implementation problems.<br>The talk will explain various building blocks for fuzz testing, namely corectness notions, generators, mutators, sanitizers, among others, and see how Forth applications can benefit from fuzzing.
Nick Nelson - Better Values	|Improvements to the implementation of the extended Forth VALUE concept