←back to thread

Stop writing CLI validation. Parse it right the first time

(hackers.pub)
203 points dahlia | 1 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 #
dcminter ◴[07 Sep 25 09:48 UTC] No.45156801[source]▶
You do you, obviously, but "now let npm work its wicked way" is an offputting step for some of us when narrowing down which tool to use.

My most comfortable tool is Java, but I'm not going to persuade most of the HN crowd to install a JVM unless the software I'm offering is unbearably compelling.

Internal to work? Yeah, Java's going to be an easy sell.

I don't think OP necessarily meant it as a political statement.

replies(3): >>45156969 #>>45158151 #>>45160329 #
1. vvillena ◴[07 Sep 25 13:51 UTC] No.45158151{3}[source]▶
This is not an issue with Java and the other JVM languages, it's simple to use GraalVM and package a static binary.