Why isn't the actor model used in the wild?

I’d argue that’s already a lot and most of what a website / webapplication needs without knowing anything more about the business case.

I dunno I’d think that more processes would be spawned for things like… properly verifying data or something… the akkoma repo hasn’t got that much either I thought elixir was about processes?

Why though? Processes and their communcation mean additional overhead. That overhead is useful where you need (failure) isolation, like e.g. between different requests being handled, but it’s not useful where that’s not the case, like within a single webrequest being handled.

I hope we won’t go in circles here once again.

Actors in Elixir generally map to runtime subcomponents of the system, not business entities. So for example when using phoenix channels or live view every connected page is an actor that manages messages in and data out, but then the business logic processing on that data favors functional data patterns.

Isn’t it technically that the actor model is used under the hood?

So the actor model doesn’t apply for business logic?

yea, under the hood.

Yea, the actor model is the engine, but you use the car to do business.

Here is a paper by Carl Hewitt, the author of The Actor Model - https://arxiv.org/vc/arxiv/papers/1008/1008.1459v8.pdf. I hope it sheds some light on this model of computation.