11–20 of 30 posts
I love Rust for systems dev, and I truly can't wait to read the article, because I can't imagine ever wanting to use it for exploratory data analysis, one-off stuff, or notebooks. Why deal with the borrow checker and compilation just to plot something in a notebook? Python is kind of ugly IMO, but it seems much quicker for prototyping.
I love Rust for systems dev, and I truly can't wait to read the article, because I can't imagine ever wanting to use it for exploratory data analysis, one-off stuff, or notebooks. Why deal with the borrow checker and compilation just to plot something in a notebook? Python is kind of ugly IMO, but it seems much quicker for prototyping.
Yes, I wanted to try Rust for this year's Advent of Code and I gave up before I figured out how to read the input file.
Earlier quoted context omitted.
In my opinion, we need a statically typed contender to R, Python and Julia. The use case is quite simple. Most data-oriented applications where you need linear algebra, probability theory, statistics do contain a significant amount of data pre-processing and business logic once extended to enter production. Here static typing is advantageous. Keeping the whole codebase in the same language is a significant advantage.…
> In my opinion, we need a statically typed contender to R, Python and Julia. Nim is getting there.
Also worth mention would be F#: https://github.com/SciSharp
Earlier quoted context omitted.
Yes, I wanted to try Rust for this year's Advent of Code and I gave up before I figured out how to read the input file.
If you give it a try again, https://doc.rust-lang.org/std/fs/fn.read_to_string.html is probably whet you want.
Result>
It's probably huge effort to somehow target examples both for newbies and advanced users. I don't know what's good solution and if it's a real problem at all.
By the way, I tried to sign up for the newsletter – since you also offered a 10% discount there, and was going to buy the book using that – but it returns with a 404 when processing via https://newsletter.datacrayon.com/subscription/form.
Earlier quoted context omitted.
In my opinion, we need a statically typed contender to R, Python and Julia. The use case is quite simple. Most data-oriented applications where you need linear algebra, probability theory, statistics do contain a significant amount of data pre-processing and business logic once extended to enter production. Here static typing is advantageous. Keeping the whole codebase in the same language is a significant advantage.…
> In my opinion, we need a statically typed contender to R, Python and Julia. Nim is getting there.
Earlier quoted context omitted.
If you give it a try again, https://doc.rust-lang.org/std/fs/fn.read_to_string.html is probably whet you want.
I wonder if this type signature may be too intimidating for newcomers: Result > It's probably huge effort to somehow target examples both for newbies and advanced users. I don't know what's good solution and if it's a real problem at all.
People in the Rust ecosystem will tell you to either unwrap the error or use https://docs.rs/anyhow/1.0.34/anyhow/ to completely ignore it. Great thing - it's simple to ctrl-f and turn your one-off code into production code with powerful errorhandling.
I love Rust for systems dev, and I truly can't wait to read the article, because I can't imagine ever wanting to use it for exploratory data analysis, one-off stuff, or notebooks. Why deal with the borrow checker and compilation just to plot something in a notebook? Python is kind of ugly IMO, but it seems much quicker for prototyping.
In my opinion, we need a statically typed contender to R, Python and Julia. The use case is quite simple. Most data-oriented applications where you need linear algebra, probability theory, statistics do contain a significant amount of data pre-processing and business logic once extended to enter production. Here static typing is advantageous. Keeping the whole codebase in the same language is a significant advantage.…
I'm not sure we really need a "contender". We need a complement. I personally use D. I love the language, I can compile my functions into a static library, and I can have R load them the same as it loads a library of C functions. It's worked well for me for years. Should work for plenty of languages, whether that's Rust, Nim, or whatever.
There are at least two reasons I've moved away from the idea of a replacement language:
- It's pretty easy to do if you already have experience with a compiled language. The benefit of a replacement language is small.
- You can move to the new language slowly, to the degree that you want, without giving up or rewriting any already working code. Others can easily use your code without having to move to that language.
Thank you for writing this! I've been meaning to get a Jupyter notebook set up with Rust. By the way, I tried to sign up for the newsletter – since you also offered a 10% discount there, and was going to buy the book using that – but it returns with a 404 when processing via https://newsletter.datacrayon.com/subscription/form .
Sorry about the newsletter - I did not expect anything near this kind of traffic, and it's hit everything :)
I've made a temporary 15% discount coupon "hnhug10" for anyone who wants/needs one!
In the meantime I need to start thinking about more resilient hosting...