Candle: Torch Replacement in Rust
github.com
Candle: Torch Replacement in Rust
1–10 of 192 posts
Re: Candle: Torch Replacement in Rust
#2Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
Re: Candle: Torch Replacement in Rust
#3Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
I agree. Two years ago, I tried writing data-intensive components for Python as rust extension modules. It was painful, tedious, and confusing.
I came back to it for a second try a month ago, and was blown away. PyO3 and maturin (especially maturin) are stunningly straightforward. I actually find maturin easier to use than “normal” Python packaging tools, to the extent such a thing even exists.
I really hope we will see a move towards rust, and away from extension modules written in C/C++/Fortran, just because the development experience is so much more approachable. Which is not something I thought I would say about Rust!
Re: Candle: Torch Replacement in Rust
#4Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
I agree. Two years ago, I tried writing data-intensive components for Python as rust extension modules. It was painful, tedious, and confusing. I came back to it for a second try a month ago, and was blown away. PyO3 and maturin ( especially maturin) are stunningly straightforward. I actually find maturin easier to use than “normal” Python packaging tools, to the extent such a thing even exists. I really hope we will…
You've convinced me. I've been waiting to see when Julia or Rust would be able to start encroaching on Python's production lockup. Time to deep dive!
Re: Candle: Torch Replacement in Rust
#5Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
"I've been wondering what might move data scientists to Rust"
I mean, writ large, the answer is "The availability of the ecosystem they need to use daily in Rust, without having to rewrite it themselves." That is more than just a torch replacement, so this won't do it for data scientists, even if Python is ... painful in a lot of ways to productionize or even use.
Maybe it'll get some started on that ecosystem, though, so that a few years from now you see larger movement.
Re: Candle: Torch Replacement in Rust
#6Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
id imagine repl, junpyter notebooks are pretty useful and not doable in rust atm
Re: Candle: Torch Replacement in Rust
#7Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
> I've been wondering what might move data scientists to Rust.
I think dynamic typing is the missing piece.
Rust's safety guarantees are great and I like the language, but the type system is a barrier for learners, especially people who aren't full-time devs. Ease of experimentation and flexibility are key for this use case.
Re: Candle: Torch Replacement in Rust
#8Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
id imagine repl, junpyter notebooks are pretty useful and not doable in rust atm
Rust in Jupyter Notebooks: https://users.rust-lang.org/t/getting-started-with-rust-jupy...
REPLit for Rust: https://replit.com/languages/rust
For general REPL and rust appears there are a few options.
I don't think getting rid of Python completely will happen. But current approaches _typically_ looks something like:
- Jupyter Notebook for custom parts of EDA
- Jupyter Notebook for testing new libraries or learning new methods
- Pipeline (replaceable with Rust) for standard EDA
- Pipeline (replaceable with Rust) for data quality
- Application/pipeline for product development
Re: Candle: Torch Replacement in Rust
#9I think the first Rust ML framework to gain massive traction will be the one that supports quantisation out of the box.
At the moment there's no Rust ML library that does what llama.cpp or ggml can do.
Re: Candle: Torch Replacement in Rust
#10Oh man. I feel like this is a really big deal. I've been wondering what might move data scientists to Rust. Outside working through rustlings and trying new projects in Rust, I wonder if having this available will be it.
> I've been wondering what might move data scientists to Rust. I think dynamic typing is the missing piece. Rust's safety guarantees are great and I like the language, but the type system is a barrier for learners, especially people who aren't full-time devs. Ease of experimentation and flexibility are key for this use case.
> Rust's safety guarantees are great and I like the language, but the type system is a barrier for learners, especially people who aren't full-time devs.
This surprises me. Hasn't everyone working with data (even at an "enthusiast" level) had to understand data types in the context of databases?