factor VS manifold

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

Considering the Amount domain types, I like the manifold project’s unit expression[1] approach where the unit and domain type are integrated and always reconciled.

1. https://github.com/manifold-systems/manifold/tree/master/man...

> I am glad to see a project that provides a robust and elegant API for building rest services in Java.

Alternatives for _consuming_ REST services is perhaps an equally interesting proposition, particularly since there are potentially potentially many consumers per service e.g., the manifold JSON project[1].

Other areas where Springboot feels overbearing include JPA/ORM support. In my view this is its greatest weakness, but like the "no one ever got fired for buying IBM" cliche, the same can be said today about Springboot.

1. https://github.com/manifold-systems/manifold/blob/master/man...