This is not right. It's more like Java -> Kotlin
> So whether you prefer Elixir or not you have to know Erlang.
Not really. You can get quite far in Elixir without knowing any Erlang.
Eventually you probably should learn to read Erlang docs (but not necessarily code) and maybe you might need to be able to read Erlang code, but this is truly rare.
> It's more like Java -> Kotlin
Not quite true either. If you want to do the analogy of a VM-based language the BEAM is not just a VM like the JVM. It plus the rest of the ERTS is an AOS.
> Not really. You can get quite far in Elixir without knowing any Erlang.
True. But eventually when you do want to go outside of the Elixir ecosystem you need Erlang to access the BEAM facilities.
The point was that Erlang is the "native language" of the "Erlang AOS" and is worth knowing whether you prefer Elixir/whatever on BEAM.
The Erlang System is actually an "Application Operating System (AOS)" (Joe Armstrong's definition) and the "Erlang language" is its "native system language". An analogy is writing Python code running on Linux but making a kernel system call through the C language interface. Here Python is your Elixir, Linux is the Erlang AOS(ERTS+BEAM) and the C language interface is the Erlang language interface.
PS: I hope you have watched the two videos i have linked to in this thread, they are well worth your time and answer all your questions.