factor VS batteries-included

My impression so far is (in general), Forth are practically limited to doing embedded/microcontroller development.

For us, web/mobile/desktop app devs, beside:

- 8th (https://8th-dev.com)

- Factor (https://factorcode.org)

Any suggestion which implementation we should look for?

Factor is also very much worth a look. Forth-style syntax, but with many of the ideas from CL and Smalltalk as well. In fact as a CL fan, I was very impressed by it. It's also quite "batteries included" a la Python.

Otherwise, and more seriously, I'm not completely sure variables are needed. Factor is quite usable (it's my favorite go-to language if I quickly need to script something), and mostly doesn't have them.

There's a note on the page from 2022-08-19, that a lot has been added to it. It also links to the github page[1] for the up-to-date changes.

I am a Lisp, April, APL/J/BQE, and Forth[2] aficionado. I did some file munging programs in Factor back in 2012 at my job to sort through theater attendance logs in Word to compile statistics.

[1] https://github.com/remko/waforth

[2] https://factorcode.org/

Is there any "battery-included" ANS Forth (more or less like Python/Go) which provides access to concurrency, networking, database, GUI, etc?

Not an embedded device programmer, but mostly deals with frontend apps, and occasionally backend, so those are very relevant to me.

Or perhaps use "non-traditional" Forths like 8th (https://8th-dev.com) or Factor (https://factorcode.org)?

Here's my day two solution using Factor

Here's a straight example: I've searched for a list of "awesome" OCaml libraries, chose "Batteries Included" which is apparently a widely-used OCaml library, and navigated to its source code on GitHub. Here's a random file:

Batteries Included got its implementation of Seq back in 2009: https://github.com/ocaml-batteries-team/batteries-included/commit/d67bfc69c79caa6b712ada4af0c6df604fb823b4

Another example is imperative control flow. OCaml and SML only have basic loops, they don't have returns, breaks, continues. You can simulate them with exceptions, even in a generic way if you use some higher-order functions. Getting good performance for these kind of returns would rely on inlining this function and optimizing local exceptions, which OCaml probably doesn't do as of now.