Contrary to others here, I would still suggest to stick with Erlang, but use Elixir's toolkit. You can use `mix`, `exunit`, release, etc... from Elixir, and th

Contrary to others here, I would still suggest to stick with Erlang, but use Elixir's toolkit. You can use `mix`, `exunit`, release, etc... from Elixir, and they can handle your Erlang codes fine. You also have better integration with editors like VSCode. The reason for sticking with Erlang is that your project can be used in both Erlang and Elixir community. But if you write pure Elixir, it's pretty hard to use it in Erlang. You can also write Elixir macro to wrap your Erlang code in an API. Not the other way around. Project structure between Erlang and Elixir is similar anyway, so it should not be too difficult to have one single project for both Erlang and Elixir code.