Re: Favorite shell
Posted: Mon Aug 11, 2008 1:25 pm
Rather than just "what is your favorite shell?" I'd be very interested in why a particular shell is your favorite...
I mean, I'd probably vote Bash - but that's just because it's what I use. It's what I use because it's what I've always used. But there's all kinds of things about it I'm not too thrilled with - the lack of anything in the way of useful datatypes tops the list. I'm also not too keen on the syntax (if/elif/fi, the use of square brackets, etc.). I like the overall concept (shared in most CLI shells) of encouraging sets of small tools that can interoperate - but I feel that without a decent set of agreed-upon datatypes backing it up, most shell problems seem to degrade into repeated parse/process/serialize steps, with "parse and serialize" taking altogether too much of the process - and so people program their scripts in Perl or something instead...
Based on my current feelings about what a shell should be, MS Powershell is probably the closest thing to what I want in a shell - though I'm not too keen on their decisions about style (the whole verb-noun thing, for instance - it's nice and consistent but way too verbose...) I'm trying to design my own shell, but getting hung up on matters of syntax and what capabilities it should have...
I mean, I'd probably vote Bash - but that's just because it's what I use. It's what I use because it's what I've always used. But there's all kinds of things about it I'm not too thrilled with - the lack of anything in the way of useful datatypes tops the list. I'm also not too keen on the syntax (if/elif/fi, the use of square brackets, etc.). I like the overall concept (shared in most CLI shells) of encouraging sets of small tools that can interoperate - but I feel that without a decent set of agreed-upon datatypes backing it up, most shell problems seem to degrade into repeated parse/process/serialize steps, with "parse and serialize" taking altogether too much of the process - and so people program their scripts in Perl or something instead...
Based on my current feelings about what a shell should be, MS Powershell is probably the closest thing to what I want in a shell - though I'm not too keen on their decisions about style (the whole verb-noun thing, for instance - it's nice and consistent but way too verbose...) I'm trying to design my own shell, but getting hung up on matters of syntax and what capabilities it should have...