Re:What I mean when I say that machine learning in Elixir is...
by OutOfHere on Thursday May 09, 2024 @08:34PM
(#40314377)
Gleam is a tooling development language, not a concurrency language. It runs away from Erlang's concurrency ecosystem. Also, its documentation, especially wrt concurrency, is sorely lacking. In its current state it would be a mistake it to use it for any distributed work, but perhaps this can change in time.
[ Parent
| on HN ]
Re:What I mean when I say that machine learning in Elixir is...
by vvpan on Friday May 10, 2024 @12:00PM
(#40320510)
Ah, I did not realize that. What is the point then? Why have a language on top of Erlang that "runs away from Erlang's concurrency ecosystem"?
Re:What I mean when I say that machine learning in Elixir is...
by OutOfHere on Friday May 10, 2024 @01:09PM
(#40321352)
Gleam has some third-party package(s) for concurrency, but I wouldn't consider them mature, and they wouldn't compare to anything like what Elixir has. It is not the primary or even the secondary focus of the Gleam language. I guess there is no point for me.
Re:What I mean when I say that machine learning in Elixir is...
by kamma4434 on Wednesday May 15, 2024 @09:20AM
(#40366556)
From what I understand, you get all of OTP as it is now – You only use the experimental Gleam packages if you want types. So you should be able to use them right out of the box, with the same level of guarantees (or lack of) that you get in Ex/Erlang.
Still, I have not yet found a compelling reason to switch over – or at least try – Gleam.