I've wanted something like this for a long time, going to take it for a spin. Looks like there is a lot of help wanted on certain underlying implementations so that would be fun to help out with too.
I think there is tremendous value in having these functions that appear stateless and run in "stateless" environments like aws lambda, but on each invocation they are handed the previous state and are able to augment it and return (to persist) or do nothing.
There’s definitely a lot of inspiration from Erlang. We’re far from the first actor-ish framework, but we’re hoping ActorCore sticks by working seamlessly with existing tools, instead of forcing people to learn a new paradigm.
We’re open to contributions – feel free to join our Discord if you have questions.
I think there is tremendous value in having these functions that appear stateless and run in "stateless" environments like aws lambda, but on each invocation they are handed the previous state and are able to augment it and return (to persist) or do nothing.
Very erlang-y, which is rad.