How does this stack up versus cheat.sh ? I really should be making use of one of these and I would prefer to learn the most useful.
Navi- an interactive cheatsheet tool for the command line
11–17 of 17 posts
Re: Navi- an interactive cheatsheet tool for the command line
#12It’s quite insane the amount of nice tooling people have been building thanks to Rust. I’m wondering why is it that Rust transitioned us to a new era for open source. My bet is the package manager.
Honestly, I think part of this perception is the fact that things developed in Rust are more likely to advertise themselves as such. For example, I know that micro text editor is developed in Go only because I checked. I have no need to know this as an end-user, but many Rust-based projects seem quite eager to highlight that.
Re: Navi- an interactive cheatsheet tool for the command line
#13It’s quite insane the amount of nice tooling people have been building thanks to Rust. I’m wondering why is it that Rust transitioned us to a new era for open source. My bet is the package manager.
Re: Navi- an interactive cheatsheet tool for the command line
#14Earlier quoted context omitted.
I wouldn't say it's a new era of open source, there's nothing novel about licensing from rust. But from a tool perspective both rust and golang support easy static binary creation and IMHO that's why you see both of them being popular with modern CLI tools. Gone are the days of packaging up distro-specific binaries, or worse yet depending on some system installed script interpreter (and all the myriad of ways it can…
> But from a tool perspective both rust and golang support easy static binary creation […] Honest question: As someone who knows C++ and CMake, what Rust and Go do to make it easier?
At least for rust (I'm not as familiar with Go), it brings super easy project setup and library inclusion.
E.g. for creating a project and running it:
> cargo new my-cli > cd my-cli > cargo run
And then all I need to do is add structopt to the cargo.toml file to bring in a command line parser with hygienic macros.
Edit: they also do static linking by default :EndEdit
‐---------------------
But what it really makes easier is not needing to worry about memory safety. C++ is good at making static binaries, even if it might be slightly more fiddly.
So it's more like the static binary is the advantage over scripted languages, and memory safety is the advantage over c++.
I would never attempt a tool in c++ now that I know Rust.
Re: Navi- an interactive cheatsheet tool for the command line
#15Earlier quoted context omitted.
I wouldn't say it's a new era of open source, there's nothing novel about licensing from rust. But from a tool perspective both rust and golang support easy static binary creation and IMHO that's why you see both of them being popular with modern CLI tools. Gone are the days of packaging up distro-specific binaries, or worse yet depending on some system installed script interpreter (and all the myriad of ways it can…
> But from a tool perspective both rust and golang support easy static binary creation […] Honest question: As someone who knows C++ and CMake, what Rust and Go do to make it easier?
Re: Navi- an interactive cheatsheet tool for the command line
#16Earlier quoted context omitted.
I wouldn't say it's a new era of open source, there's nothing novel about licensing from rust. But from a tool perspective both rust and golang support easy static binary creation and IMHO that's why you see both of them being popular with modern CLI tools. Gone are the days of packaging up distro-specific binaries, or worse yet depending on some system installed script interpreter (and all the myriad of ways it can…
> But from a tool perspective both rust and golang support easy static binary creation […] Honest question: As someone who knows C++ and CMake, what Rust and Go do to make it easier?
Re: Navi- an interactive cheatsheet tool for the command line
#17It’s quite insane the amount of nice tooling people have been building thanks to Rust. I’m wondering why is it that Rust transitioned us to a new era for open source. My bet is the package manager.
Honestly, I think part of this perception is the fact that things developed in Rust are more likely to advertise themselves as such. For example, I know that micro text editor is developed in Go only because I checked. I have no need to know this as an end-user, but many Rust-based projects seem quite eager to highlight that.
* you can reuse (parts of?) it in your project easily
* it will be fast
* you can contribute to it easily