Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Whenever you message another process and need a reply there is a risk of deadlock.

There are edge cases, sure, but I have yet to encounter a deadlock after 7 years of professional work with Elixir.

> I didn't find any primtives in OTP for handling this

See `GenServer.call/2`. This covers 99% of call/return patters in distributed systems. I take it you haven’t written much (any?) Elixir because you would have found this function.

> The actor model doesn't really offer any benefit over other models while bringing significant downsides.

Actors are a way better abstraction for pretty much any application-level code I can think of. I say this having written Go, Rust, and Elixir. What downsides are you talking about specifically?

> Plus, there are major downsides to using an unpopular platform like Erlang/BEAM.

The BEAM is popular. At least 3 different serious languages use it. What down sites are you waving your hands up here?



>> Plus, there are major downsides to using an unpopular platform like Erlang/BEAM.

> The BEAM is popular.

At this point I'd say it's more popular than ZIO, an effects/io/concurrency library basically implementing its own language and threading model on top of Scala




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: