2 ms·
Yes and that's a lot of work for what would be a two-liner in JS. Every time someone says "just make a process and a supervisor, put it elegantly in the superv
by skrebbel 8y ago
Yes and that's a lot of work for what would be a two-liner in JS.
Every time someone says "just make a process and a supervisor, put it elegantly in the supervisor tree, go think through the failure modes, ponder a bit about these 3 or 4 edge cases and potential race conditions, and you're done! hooray!" I get a bit grumpy.
Elixir is awesome, but there's a simplicity to a single-threaded execution model that takes away a lot of the things that make concurrency hard.
- polmuz 8y agoAt the small prize of parallelism. And now that you are dealing with workers, task queues, etc. a native process + supervisor solution doesn't seem bad at all.
- skrebbel 8y agoIt's not a contest! All I'm saying is that there are things that Elixir isn't the best at. Is that so weird? I feel like everybody responding to me has this strong emotional need to defend Elixir. Why? it's just a tool. Like any tool it has pros and cons.
- cultofmetatron 8y agoElixir is amazing at creating parrallelized network heavy iobound applications. obviously its going to be shit if you want to do machine learning or anything computationally bound. Thats why it has amazing first class integrations! https://github.com/fazibear/export https://github.com/fazibear/export and https://github.com/hansihe/rustler https://github.com/hansihe/rustler