On Tue, 17 May 2005, Steve Holdoway wrote:
On Tue, May 17, 2005 1:01 pm, John Carter said: [snip]But _pleeze_ let's nail these old "*sh" horrors into nice lead lined coffins now. Preferable with a nice industrial strength wooden stake to ensure they don't emerge again.
At most let's have a brief chat on "nifty command line tricks you can do in zsh or bash" and lets stop there. I can do the bash one.
Horses for courses.
I honestly believe from fairly extensive and bitter experience that the only courses I would actually choose to run *sh horses on are as a command line or a very old legacy server that doesn't have a port of a decent language.
What else would you write your backup scripts in?
Anything more complex than a verbatim "file of commands" I write in Ruby, much easier, much more maintainable, far less trouble.
If you were to choose something like perl or python instead, I would understand and make no complaint. But the *sh, no thanks! I wish the UN*X's would evolve away from them.
Yes, I know they are "grandfathered" in place, but that is something that is crippling Un*x evolution, rather than an advantage of the *sh.
John Carter Phone : (64)(3) 358 6639 Tait Electronics Fax : (64)(3) 359 4632 PO Box 1645 Christchurch Email : [EMAIL PROTECTED] New Zealand
We all live but seconds away from pain and death, yet we live as though it wasn't even possible.
We are but one person amongst 6 billion, yet we live as though we, personally, matter.
So, as you were saying... how real did you want me to get?
