Crate ideas

[umbrageodotus]

Hey! I'll get straight into it.

1. (compio)[https://compio.rs] instead of glommio - glommio is unsound/unsafe and compio allows for more than io-uring (IOCP too)
2. The hickory set of crates - would be good to add a DNS section (see also: Is there any dns crate(both server/client) to be added? #92 )
3. Argh - a great opinionated parser, imo.

Thanks,
Alex <3

[djc]

1. (compio)[https://compio.rs] instead of glommio - glommio is unsound/unsafe and compio allows for more than io-uring (IOCP too)

glommio has 11k recent downloads vs 42k for compio, so it probably makes sense to drop glommio for compio.

2. The hickory set of crates - would be good to add a DNS section (see also: Is there any dns crate(both server/client) to be added? #92 )

I'm a Hickory DNS maintainer so not impartial, but I think adding a DNS section mentioning Hickory would make sense. hickory-resolver has 8.6M recent downloads so it's pretty popular.

3. Argh - a great opinionated parser, imo.

We already have clap, bpaf, lexopt and pico-args. I don't think we should add more, though we could decide to replace some?

Recent downloads:

1. clap: 76M
2. pico-args: 6.6M
3. argh: 1.1M
4. lexopt: 1.1M
5. bpaf: 750k

I think argh and bpaf offer a similar (derive-based) experience, so switching out bpaf for argh probably makes sense.

Do you want to send some PRs?

[umbrageodotus]

@djc But bpaf isn't really opinionated, is it...? And yes, compio is just the goat (doesn't matter than I'm currently working on merging changes that improve code quality buttt)!

I can send a PR if you want, not sure how soon since I have other stuff to work on.

[pacak]

I think argh and bpaf offer a similar (derive-based) experience, so switching out bpaf for argh probably makes sense.

Experience is different though.

For the developer - argh is just derive, somewhat limited at what it can do: say you can't express - "app takes 3 named arguments, user must pass exactly two of them". With bpaf you can fallback to combinatoric interface and usually express whatever you want.

For the user - it argh does not implement posix conventions, it implements Fuchsia specification. For example you can run cargo example using either cargo run --example simple or cargo run --example=simple (clap follows posix conventions), Fuchsia spec accepts only former, but not later.

[umbrageodotus]

Yeah... because it's opinionated...

[pacak]

Yeah, just not in a good way. Otherwise I wouldn't be using a local fork of cargo-machete that swaps out the cli parser...

[umbrageodotus]

That's... an opinion! :P

[umbrageodotus]

What about gumdrop though?

[pacak]

gumdrop? Last release 3 years ago, shares some problems as argh - doesn't support non-utf8 files. It probably made some sense back in clap 2 days, but now... The project is not well, check tickets/PRs.

No pico-args either - it can silently accept invalid input.

[djc]

Sounds like we're keeping bpaf for now.