3 ms·
Can someone explain why people are creating so many CLI tools (with a very weird and custom syntax) to extract JSON using a very complicated one line command w
by IceWreck 4y ago
Can someone explain why people are creating so many CLI tools (with a very weird and custom syntax) to extract JSON using a very complicated one line command when you can make one off scripts to do the same using python/go/ruby/node/whatever ?
- QuikAccount 4y agoI'd argue that it is less about practicality and more about learning a language by recreating a CLI tool.
- UncleEntity 4y agoI wrapped boost::property_tree in a python module to read in a rss xml feed and store the items in a json file to track the TV shows I download all because the pure python version was kind of slow. The amount of time I spent on getting all that working is probably a lot less than waiting a few extra seconds on a python script I run every few days so…
- NAR8789 4y agooneliners are generally nicer for fast data exploration than one-off scripts. With a oneliner I can get started instantly, and build incrementally. With a one-off script my first step is boilerplate input handling. Maybe a nice middle ground would be for more language runtimes to have an equivalent to perl's `-p` flag. https://perldoc.perl.org/perlrun#-p https://perldoc.perl.org/perlrun#-p This flag is so convenient that I mostly use `perl -pe` instead of `sed` for regex search-and-replace.