From Python to Elixir Machine Learning
thestackcanary.com
From Python to Elixir Machine Learning
1–10 of 89 posts
Re: From Python to Elixir Machine Learning
#2At first I thought what does Nx (nrwl/nx) has to do with machine learning, then I figured context is about Elixir lib named Nx.
Naming things is hard.
Re: From Python to Elixir Machine Learning
#3Instead of moving to Elixir I believe it makes more sense to wait/move to Mojo when it's ready:
Re: From Python to Elixir Machine Learning
#4Instead of moving to Elixir I believe it makes more sense to wait/move to Mojo when it's ready: https://www.modular.com/mojo
Elixir (NX) is ready now, Mojo might be, at some time in the future....
also Mojo won't have the BEAM or ergonomics around Functional Programming.
Re: From Python to Elixir Machine Learning
#5I wish there wouldn’t be such a song and dance about “moving away from Python”. There’s nothing wrong with creating ML tools in Elixir, but it’s always Python is slow, Python has no concurrency support, blah blah
Re: From Python to Elixir Machine Learning
#6I wish there wouldn’t be such a song and dance about “moving away from Python”. There’s nothing wrong with creating ML tools in Elixir, but it’s always Python is slow, Python has no concurrency support, blah blah
"Everything is working fantastically with our python ML project but we're rewriting it in Elixir anyway" would be a weird article wouldn't it?
Re: From Python to Elixir Machine Learning
#7I wish there wouldn’t be such a song and dance about “moving away from Python”. There’s nothing wrong with creating ML tools in Elixir, but it’s always Python is slow, Python has no concurrency support, blah blah
Those are real issues though.
Re: From Python to Elixir Machine Learning
#8Instead of moving to Elixir I believe it makes more sense to wait/move to Mojo when it's ready: https://www.modular.com/mojo
Elixir (NX) is ready now, Mojo might be, at some time in the future.... also Mojo won't have the BEAM or ergonomics around Functional Programming.
ML is not an island, it is part of a much broader "data science" universe that is currently served fairly well (still imperfectly) by the Python/C++ stack and is not easy to replicate.
Throwing BEAM or FP acronyms around won't really strike a chord with people working with data and models.
Mojo will (as per promise) tap into the wider ecosystem. Other platforms are more than welcome to try but this ultimately requires a huge community of scientists / developers to become a real alternative.
Re: From Python to Elixir Machine Learning
#9Re: From Python to Elixir Machine Learning
#10Earlier quoted context omitted.
Those are real issues though.
Is concurrency useful for ML?
You end up having to do a lot of things in a ML training run, some of which you can do in parallel because it’s not important now (eg saving metadata) or because you’d otherwise be resource limited (eg loading data and formatting batches for training)