for command line apps bash, python, perl, ruby and similiar high level languages are more than enough. You can write some Kali Lincox the louder you are the less you hear network probe stuff with any of these, or even a storage optimizer (BleachBit is almost entirely written in Python, which is a very highly abstracted language implemented from C) Rust and C are only needed for performance-crtitical stuff (like rythm games) or/and directly interacting with hardware (drivers, firmware, system functions)
I would not throw Rust and C together in this.
Rust is low-level in terms of being usable for kernel and embedded development (due to not needing a runtime), but it’s rather high-level in terms of the syntax offering lots of abstraction from the weirdness of the hardware.
Some of that not-needing-a-runtime does bleed into the syntax, but in my opinion, it’s still higher level from a syntax perspective than Bash et al, because it brings in many functional aspects.
I guess, I’m also just bothered by you saying, you don’t ‘need’ Rust for writing CLIs, when it’s my favorite language for this.
To some degree, I do just find it ridiculous to launch a whole runtime when the user just wants the --help, but the argument parsing in Rust is also just really nice: https://rust-cli.github.io/book/tutorial/cli-args.html#parsing-cli-arguments-with-clap
for command line apps bash, python, perl, ruby and similiar high level languages are more than enough. You can write some Kali Lincox the louder you are the less you hear network probe stuff with any of these, or even a storage optimizer (BleachBit is almost entirely written in Python, which is a very highly abstracted language implemented from C) Rust and C are only needed for performance-crtitical stuff (like rythm games) or/and directly interacting with hardware (drivers, firmware, system functions)
I would not throw Rust and C together in this.
Rust is low-level in terms of being usable for kernel and embedded development (due to not needing a runtime), but it’s rather high-level in terms of the syntax offering lots of abstraction from the weirdness of the hardware.
Some of that not-needing-a-runtime does bleed into the syntax, but in my opinion, it’s still higher level from a syntax perspective than Bash et al, because it brings in many functional aspects.
I guess, I’m also just bothered by you saying, you don’t ‘need’ Rust for writing CLIs, when it’s my favorite language for this.
To some degree, I do just find it ridiculous to launch a whole runtime when the user just wants the
--help, but the argument parsing in Rust is also just really nice: https://rust-cli.github.io/book/tutorial/cli-args.html#parsing-cli-arguments-with-clap