rust-prehistory VS argh

There’s a rust-prehistory repo preserving Rust’s compiler code at very early stage. You can see how Rust looks like at that time.

https://github.com/graydon/rust-prehistory is another good resource, particularly the doc/notes directory. All kinds of good stuff in there that looks pretty different than today. I also liked Marijn's talk, The Rust That Could Have Been.

There's also this repository depending how far back you want

If, on the other hand, you’re interested in pre-modern Rust, there’s always this repo: https://github.com/graydon/rust-prehistory

For some snapshots on the history of the language up to 1.0 check out: https://brson.github.io/archaea/. For some really ancient stuff check out the graydon/rust-prehistory/ repo. Also looking at the oldest commits and issues on the Rust repo can be pretty interesting. It's a great public resource.

As Graydon Hoare notes in the comments on GitHub this wasn't the first repo so the real history goes back even further. He's also shared a "prehistory" repo [1] which is interesting to browse. The first commit [2] in _that_ repo is from 2008 but Graydon mentions starting work back in 2006.

Anyway in a sense this repo represents Rust in the real world rather than in gestation, so seems apt to call it the birthday.

[1] https://github.com/graydon/rust-prehistory

[2] https://github.com/graydon/rust-prehistory/commit/1969e085e3...

Early Rust was very different (example). It is almost certain that modern Rust took a lot of cues from Go. And, as above, Go was obviously heavily inspired by C, just like your language. So, all told, where you landed is likely very much what is expected.

The pre-git history was imported as https://github.com/graydon/rust-prehistory

Two other links related to ancient Rust:

* https://github.com/graydon/rust-prehistory -> the code from before the rust-lang/rust repo

* https://youtube.com/watch?v=79PSagCD_AY -> a talk I gave around the 1.0 release giving my personal perspective on the history.

Oh heck, one more fun one: https://github.com/brson/archaea

https://github.com/google/argh is another minimal library for CLI argument parsing that could be in the list

My go-to is argh[1], as it's more lightweight while still providing a nice derive-based API.

[1]: https://github.com/google/argh

It'll panic if the path contains non-UTF8-able bytes.

Yes clap needs a lot of boilerplate that small programs don't always need, but if you're going to simplify it, I don't think having a bunch of arguments given to the main function is better than having an option struct as in argh. Such an option struct can be given to other functions from the main, can have dedicated consistency check or completion methods, etc.

Typically programs are configured through a config object. People like to use things like clap, structopt, or argh for passing in arguments through the CLI https://github.com/google/argh. You can also use the env! macro for embedding values in at compile time, or by going through the std::env::var infrastructure for runtime env vars.

Until the argh crate bumps their version I cannot updater the version on crates.io so the install command currently is: cargo install --git https://github.com/mkatychev/darkroom

Ahh. The secondary reason I discounted Argh as "unsuitable for purpose" after "Doesn't support using OsString under the hood".