Yeah you'd need to learn it, but it's like any other tool.
unfamiliarity? Plus the problem of 'nobody ever got fired for running IBM' plaguing your work.
I highly recommend the talk The Soul of Erlang and Elixir by Sasa Juric which shows off the essence of the BEAM.
Uncaught throws, hanging errors - while someone much smarter than I could have done it better, I was doing a lot of async/retry of APIs with high failure rate and the BEAM just made it easy.
I’ve got massive hopes for things like Bun, but especially Deno’s architecture of message passing, but I’m now humbled by my not knowing that existed in V8.
From the whole zoo of system probing stuff or the downright amazing dynamic tracing.
Have a quick look at https://www.erlang-in-anger.com/
If you are writing a distributed system with plenty of microservices BEAM will be magnitudes easier to debug if you write the same system in BEAM native
I’d love to hear from anyone running it in production.
I have always been BEAM-curious, but never felt comfortable running it in production, as it feels like a big black box, and I’m not confident that I’d be able to diagnose problems as readily as I can in .NET, Go, or Node. I’m not sure why I feel that way about BEAM.