Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is exactly what the BEAM and OTP do for Erlang/Elixir IMO.

In order to have parallel programming work effectively, you have to enforce a set of rules that ensures it always works reliably. You can’t add it on after the fact and that’s why it’s such a hard problem outside of the BEAM.



I dont know much at all about erlang but if it cracked this shouldnt it be more prominent in HPC type applications? Is there some other tradeoff?


There were some tradeoffs that caused heavy computations to be a concern for many years. Elixir Nx recently tackled the problem and is probably a worthwhile read if you're curious.

https://github.com/elixir-nx

https://dashbit.co/blog/elixir-and-machine-learning-nx-v0.1


It's slow, so while concurrency is great, it will never replace the core libraries written in C, C++, or FORTRAN.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: