Re:Rich Command Shells
by tubelite on Friday October 10, 2014 @06:21AM
(#8437020)
It's the old "if you have a hammer, everything looks like a nail". Since I'm a filesystem engineer, everything looks like a file :)
Seriously though: the file is a powerful and familiar abstraction. The primary motivation for pigshell was to provide a common minimum abstraction across different web APIs which would enable basic data movement and backup.
That said, pigshell commands actually pass objects across the pipeline; files are a kind of object. For instance,
cat http://pigshell.com/sample/life-expectancy.html | table2js -e "tr" foo country data | head | printf
extracts data from an html table, converts them to plain Javascript objects and prints their json representation.
Seriously though: the file is a powerful and familiar abstraction. The primary motivation for pigshell was to provide a common minimum abstraction across different web APIs which would enable basic data movement and backup.
That said, pigshell commands actually pass objects across the pipeline; files are a kind of object. For instance,
extracts data from an html table, converts them to plain Javascript objects and prints their json representation.