|
|
|
|
|
|
by cube2222
2971 days ago
|
|
|
That's exactly the problem I have with elixir, or akka for that matter. It's definitely a very convenient abstraction for building microservices and distributed systems, but at the same time it's a heavy language lock-in you're getting yourself into, the moment you start your project. And especially now, when there are the de facto standard libraries to do various tasks (like TF in Python) I think language lock-in can be a terrible idea. |
|
|
If I need to do something in Python, I have options like pyrlang[0] and rabbitmq[1].
In fact, parsing in Elixir is not nearly as mature as what is provided in Python. I need to parse emails. Python has `email.parser` which is perfect for my use case. I can easily use Pyrlang to do this. But Elixir is still much better at being an email client (or many email clients). The end result is an email client in Elixir that uses Python to parse the emails.
When I started with Elixir, my goal was to use it as much as possible, but delegate as soon as the task is better handled in another language.
[0]:https://github.com/esl/Pyrlang [1]:https://www.rabbitmq.com/