←back to thread

Stop writing CLI validation. Parse it right the first time

(hackers.pub)
203 points dahlia | 2 comments | 06 Sep 25 18:20 UTC | HN request time: 0.409s | source
Show context
bschwindHN ◴[07 Sep 25 09:25 UTC] No.45156696[source]▶
Rust with Clap solved this forever ago.

Also - don't write CLI programs in languages that don't compile to native binaries. I don't want to have to drag around your runtime just to execute a command line tool.

replies(9): >>45156782 #>>45156785 #>>45157057 #>>45157203 #>>45158148 #>>45159646 #>>45160365 #>>45161166 #>>45163035 #
1. geon ◴[07 Sep 25 23:06 UTC] No.45163035[source]▶
This seems like a really weird stance. Who are you to dictate what language people should use? Why CLIs in particular?
replies(1): >>45165616 #
2. bschwindHN ◴[08 Sep 25 07:46 UTC] No.45165616[source]▶
I'm just making an opinionated suggestion for the case when you're shipping a tool to end users and you don't want the tool to suck. Attaching a python or nodejs runtime to your tool is a quick way to make it suck for end users. It's laziness on the dev's part who didn't bother learning a better tool for the job.