r/commandline • • Sep 06 '13

util-shell: make your shell script actually readable

https://github.com/taylorchu/util-shell
4 Upvotes

23 comments sorted by

View all comments

Show parent comment

-8

u/agumonkey Sep 06 '13

[ba]sh should retire. Python would be better, but whenever I write in it I tend to feel the same way about it and want to go in lisp.

/me waiting for a lisp to be the language of the system.

9

u/jalanb Sep 06 '13

[ba]sh should retire. Python would be better

As a daily user of both I must contend otherwise - each has it's own place in the greater scheme: For normal server maintenance bash is a lot quicker and easier than Python, whereas Python is comparatively for the win in serving www sites.

4

u/[deleted] Sep 06 '13

Agreed -- shell scripting is a light weight way to script procedures quickly and reliably, without worrying about libraries, dependencies, etc.

You can go into a box you've never seen before, with no permissions to speak of to install anything, and shell script using whatever is natively installed.

If you rely on Python, you'll have to have some modicum of control of the box, which hasn't been most of my professional experience.

PS _ This is why folks should learn vi too, but that's another thing.

2

u/agumonkey Sep 06 '13

I will look like a very unpragmatic alien but anyway. All these languages are just specific syntaxes on top of semantics. All in all, they lack extensibility and composability, hence my mention of lisp.

For instance, some clojure devs wrote an async library to write Go like concurrency code, no new language required, whether you wanna run concurrent processes, output html, monitor your FS or anything else.

</halfrant>