4 ms·
> As someone who has worked two jobs now writing, deploying, and operating Erlang clusters, I recommend switching to Rust. I'm surprised to read this, Erlang a
by dxhdr 8y ago
> As someone who has worked two jobs now writing, deploying, and operating Erlang clusters, I recommend switching to Rust.
I'm surprised to read this, Erlang and Rust have almost nothing in common. It's understandable that BEAM doesn't suit your needs but suggesting that everyone should write Rust instead is grossly misleading. They are suited to solving different problems!
- ilovecaching 8y agoThey have a lot in common syntactically, semantically, and philosophically. They are both languages designed to promate safety and robustness. They're both suitable for writing highly concurrent, massively scale-able applications. The future is lots of cores, and the Rust community is on board with this. I'd also like to point out that at both of my jobs, we used Erlang for uses cases that are most heavily associated with the language, and for which popular open source alternatives in Elixir/Erlang already exist. We have had better success scaling, operating, and hiring for Rust. We've saved man hours, time, and money. So I am saying that Rust is a replacement for Erlang. It's not a tool for a different problem.
- steveklabnik 8y agoEarly Rust was much closer to Erlang, but it lost more and more of it over time.