Hmmm, maybe I can move some of my shell scripts over to #Rust using #RustScript:
https://www.kurtlawrence.info/blog/gufdjkjkq7wphfhkvrumcvmqdr4r69
I initially thought about doing that with Go since Go is a bit more ergonomic for just spiffing out code IMHO, but the tooling around Rust is simply surpassing Go at an incredible pace.
@ljrk http://www.nushell.sh is maybe a useful alternative too.
Written in #rust and the language is rust-like with structured data piped between each command.
@zenora @ljrk Yeah, I am obviously a buge Rust fan, but I like to leave shell scripting to shells. Personally, my shell scripts (under 100 lines) are written in Fish (which is being ported to Rust). But Nu is also a good option.
For anything bigger than that, I would just write a tiny Rust CLI like stw:
@mo8it @zenora @ljrk I think I'll probably use this for some one-off smallish programs that I write occasionally that are fairly processor intensive due to the combinatorics involved. Setting up separate rust projects for each one seems awkward. I've so far resorted to python for these, but then some of them can take hours to complete. And other times, if I'm sure it will take a while, in C++ using the old `g++ file.cpp && ./a.out` approach.
