We have a whole working group this year focused on making the experience of writing CLIs awesome, so hopefully we’ll see even more great tools in the future!
I need to try implementing the string thing. It'd be a lot more fun to try to compete on speed if we were the same on accuracy.
Can you explain what you mean by this? Something like the people are going to focus on language and library features that help with writing CLIs? Or something else?
Asking because CLIs are one of my interests.
You can reach out to us on gitter [3].
[0]: https://github.com/rust-lang-nursery/cli-wg/issues
[1]: https://github.com/rust-clique/ and https://github.com/assert-rs/
[2]: https://rust-lang-nursery.github.io/cli-wg/index.html
[3]: https://gitter.im/rust-lang/WG-CLI
The areas we're trying to finish up for Rust 2018 Edition:
- Get clap (arg parsing) to 3.0 [4]
- Get assert_cmd [5] / assert_fs [6] to 1.0
- Finish work on man-page generation [7]
- Make it easier to package binaries [8] and document the CI for it [9]
[4]: https://github.com/rust-lang-nursery/cli-wg/issues/41
[5]: https://github.com/assert-rs/assert_cmd/
[6]: https://github.com/assert-rs/assert_fs
[7]: https://github.com/rust-lang-nursery/cli-wg/issues/38
Rust has different community working groups that focus on improving the Rust ecosystem in different ways this year: https://internals.rust-lang.org/t/announcing-the-2018-domain...
The TL;DR is that loc is faster by a few hundred milliseconds depending on repository size, but as cgag mentions doesn't have comment in string detection so can be quite off in its metrics, for example on the Rust repo Tokei says it has 643,754 lines of code where as loc says it's 635,849.
[0]: https://github.com/Aaronepower/tokei/blob/master/COMPARISON....
New and not-popularly adopted languages tend to have more senior people learning and developing software using them; this leads to people (read: recruiters) looking for the people with experience.. People equate the quality of software with something innate with the language, or that the developers are exceptional. Then after being popularly adopted it slumps in perceived elegance and goes on a downward spiral until it ends up like PHP, Ruby or JAVA. (not to undersell the folks who predominantly use those languages, I'm just picking languages that I've seen follow this pattern)
Also, I don't know Rust (but have read that it is somewhat difficult to learn); for the basics, FreePascal (FP) may be easier than Rust to learn and start using, because although it (FP) has advanced language features, for many basic CLI programs, the simpler procedural features should be enough.
Do you have any docs on what you mean by extensibility here? I’m curious!
[0] https://hexdocs.pm/mix/Mix.Task.html [1] https://github.com/jhartwell/Plsm
GCC's static linking issues with glibc don't apply to other compilers.
You just have to look properly for those options.
The only thing is that not all of them are free beer.
The name may not have aged well...
I manually counted a few files for comparison, I believe tokei doesn't understand python-doc-comments and think it's code.
Would you suggest me to learn Rust in order to write CLI programs? I'm also looking at haskell for the same but after this thread, I'm really thinking of going the rust way. Ideas?
I don’t think of Haskell as the best language for command line dev, but I’m far from expert in either language.
Another one potentially for this list is tokei[1] I was trying to count the code in our repos at work and used the venerable 'cloc' utility. It took over 5 minutes. Looking around I found tokei, written in rust. Same-ish results (more accurate actually) took 10 seconds.
1. https://github.com/Aaronepower/tokei