4 ms·
> why not just go with python? I can't speak for anyone else, but for me, it's because Python is cumbersome for doing the sorts of things that are easy in a sh
by professoretc 5y ago
> why not just go with python?
I can't speak for anyone else, but for me, it's because Python is cumbersome for doing the sorts of things that are easy in a shell. You want to capture the output of a command, parse it as a tab-separated table, extract the 3rd and 4th columns, and then use them to create new users with the values supplying usernames and passwords. Can you do that easily in Python?
- int_19h 5y agohttps://amoffat.github.io/sh/ https://amoffat.github.io/sh/
- hnarn 5y ago> Can you do that easily in Python? I'm not arguing for Python over bash, I'm asking about the value of zsh as opposed to bash or python. So why couldn't one do what you describe in bash? The answer probably is you very well could. So why use zsh for scripting?
- LordDragonfang 5y agoFor all its syntactic sugar, dealing with files in python (which comprises probably 90% of what I open a shell for) still requires a fair amount of boilerplate. Which is good for a general scripting language, but makes it poor for the the kind of tasks I expect of a shell.