←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: 0s | 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 #
majorbugger ◴[07 Sep 25 09:44 UTC] No.45156782[source]▶
I will keep writing my CLI programs in the languages I want, thanks. Have it crossed your mind that these programs might be for yourself or for internal consumption? When you know runtime will be installed anyway?
replies(2): >>45156801 #>>45157855 #
1. bschwindHN ◴[07 Sep 25 13:07 UTC] No.45157855[source]▶
That's fine, I'll be avoiding using them :)
replies(1): >>45158210 #
2. perching_aix ◴[07 Sep 25 13:59 UTC] No.45158210[source]▶
You'll avoid using his personal tooling he doesn't share, and his internal tooling he shares where you don't work?

Are you stuck in write-only mode or something? How does this make any sense to you?