19:52:36pjbI started lisping before they wrote those libraries.
19:55:47hexologydo you have a recommendation for a good "default" for new projects?
19:57:09kevingalThis one looks gud: https://github.com/libre-man/unix-opts
19:57:30kevingalI bookmarked it in case I ever needed a CLI parser, anyway.
19:57:58Xachhexology: to date i usually roll my own, which i find a little faster than understanding a library one. i mostly just pop things off the command line list and check against known strings like "--help" and such. i know a library can make it easier if you do it a lot or want to be more declarative.
20:00:56AnimalClatterhexology: Have you seen this recent discussion? https://www.darkchestnut.com/2021/list-command-line-argument-parsers/
20:01:06hexologykevingal: thanks, that one looks similar to adopt
20:01:12hexologyi have not AnimalClatter, thank you
20:07:00hexologyXach fair enough. command line parsing is the kind of thing that i don't want to have to think about much, for me it's easier to learn a library than to redo it from scratch, because i want my command line tools to be powerful
20:07:25hexologyi want power! auto-generated --help and --version, "-" meaning "read from stdin", etc.
20:07:42hexologyi'm too slow to do all of that by hand every time
20:10:38hexologyclon looks interesting... seems like a lot of thought has gone into it