Re:Actor system for the JVM developed by Electronic Arts
by zo1 on Thursday April 28, 2022 @02:43PM
(#31196528)
So much this. This "actor model" thing as described by GP sounds like plain old OO and RPC with extra steps and also distributed. This may be a low-effort post on my part, but I'm 100% not impressed because it sounds like marketing fluff and an opportunity to rewrite native/built-in things using frameworks. Also justifying Yet Another Framework or tool hosted on an .IO domain (snarky I know) for promotions and endless blog posts.
[ Parent
| on HN ]
Re:Actor system for the JVM developed by Electronic Arts
by macintux on Thursday April 28, 2022 @04:39PM
(#31197928)
Erlang is decades old, a highly successful (for a relatively niche language, anyway) proof that the actor model (or something approximating it) can be a great tool.
Re:Actor system for the JVM developed by Electronic Arts
by astrange on Thursday April 28, 2022 @05:03PM
(#31198186)
CSP/actors is from the 70s, like most CS. It is sort of the original OO, but that's because OO is a newer version that's both less powerful and over-complicated.
It doesn't need to be distributed, and it's better not to include that because the approach to error handling gets a lot easier. If you're distributed every call can fail, be randomly slow, has marshaling costs, is untrusted, etc.
Re:Actor system for the JVM developed by Electronic Arts
by imtringued on Friday April 29, 2022 @03:11AM
(#31202274)
I don't know what you mean by "rewrite native/built-in things using frameworks", the things you are talking about require using frameworks. You need a framework for RPC. You also need a framework for distributed shared memory.