Looks pretty interesting. Anyone had experience with this language?
I pesonally dislike that: every actor is single-threaded .
I guess it makes some things easier, both for the language as well as for the user. Also, you could argue that Pony’s actors are meant to separate work into single threads, but I think you’d be right to say this is a limiting design decision.
Oh, yes, it definitely makes things easy for pony-developers.
But it also, likely, means “no thread API, sorry. We’ll manage threads for you, in form of actors”.
Usually, actors are light-weght entities, and it is possible to spawn millions of them, literally. In “every actor is a thread” design, that is not true.
PS. I’m author of C++ actor framework named rotor, and there actors and threads are “orthogonal”
If you’re deliberately doing such work in C++, I suppose you already forgot more about parallelism & concurrency than I’ll ever know. ;)
I know though that actors and threads are not synonyms. All I wanted to point out that I see why one might want to design them as one thing.
deleted by creator
deleted by creator
