3 ms·
It's fairly pointless to compare the library to CLI libraries for other languages. It's much more meaningful to pick a language that fits the main purpose of t
by aepiepaey 9y ago
It's fairly pointless to compare the library to CLI libraries for other languages.
It's much more meaningful to pick a language that fits the main purpose of the program, and not depending on what CLI libraries are available.
Generally, the CLI interface will be a fraction of the code in an application. When deciding on a CLI library, it's usually the case of "I'm writing this application that does X, and now it requires a CLI interface - which one do I pick?".
Of course it can still be useful to review how libraries for different languages work, in order to get ideas for making a better one (or improving existing ones).
So, what makes this better than e.g. Thor or Click is that if you're in the target group, you're already using node, making the other mentioned libraries irrelevant.
- dragonwriter 9y ago> t's much more meaningful to pick a language that fits the main purpose of the program, and not depending on what CLI libraries are available. It's possible for providing a CLI to be a significant part of the main purpose of the program; e.g., if the program is largely a client CLI for a web service, other than having a language with a reasonably usable web requests library, there's not a lot beside the CLI-building tools guiding the choice.