http://tech.saigonist.com/taxonomy/term/41/all en http://tech.saigonist.com/b/code/choosing-shell-script-vs-python-vs-nodejs-vs-php-server-side-command-line-scripting <span class="submitted-by">December 22, 2015</span><div class="field_tags"><span class="label label-info"><a href="/tags/nodejs">node.js</a></span> <span class="label label-info"><a href="/tags/python">python</a></span> <span class="label label-info"><a href="/tags/php">php</a></span> <span class="label label-info"><a href="/tags/shell">shell</a></span> <span class="label label-info"><a href="/tags/bash">bash</a></span> <span class="label label-info"><a href="/tags/javascript">javascript</a></span> </div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>After decades of improvements in graphical user interfaces, the Unix command line interface still remains the most powerful way to get things done for a lot of workflows. This is due to many reasons: the difficulty of quickly and precisely moving the mouse cursor compared to the ability of touch typists to select exactly what they want (even when it's via hotkey combinations), but mainly (IMO) the expressive power of composing separate Unix commands into one pipe-separated command operating on standardized files (usually text).</p> <p>It's also easy to write your own Unix commands which...</p></div></div></div> Tue, 22 Dec 2015 09:07:59 +0000 tomo 20 at http://tech.saigonist.com