>>19 ksh is the hipster one. And I doubt they'd switch, because being GNUterd is worse than being accused of racism.
zsh is the shell that everyone criticizes in public for being too big (even though it's smaller than bash), but then secretly uses because it's vastly superior.
Name:
Anonymous2012-11-01 18:34
I hate dubs
Name:
Anonymous2012-11-01 18:35
>>21
Is it as idiosyncratic as sh/bash? Is there a shell somewhere that doesn't have ass-backward syntax and extremely limited support for arrays and more complex data structures? I'd like to use scsh, but I'm not sure how good it is.
Is it as idiosyncratic as sh/bash?
Unfortunately, yes. It's syntax is based on Bourne shell syntax.
Is there a shell somewhere that doesn't have ass-backward syntax and extremely limited support for arrays and more complex data structures? https://github.com/frytvm/XS
>>13,21
The nice thing about ksh is that it knows when to stop.
The entire concept of "expansion" is the worst thing about shell languages. bash and zsh address this problem by... adding more types of expansion. That's some wonderful thinking right there.
ksh says, let's keep only the ugly stuff that Bourne compatibility requires us to have, and add new control constructs to so we can use as little of said ugly stuff as possible. It's the only new shell language that has the decency to admit its limitations, and that's why I like it.
>>1 At the FSF, Fox authored GNU Bash, GNU Makeinfo, GNU Info, GNU Finger, and the readline and history libraries.
Somewhere deep inside I always knew all these abominations had to be the handiwork of a single individual.
>>14,23
Stick with AWK and KSH93. You really do not need anything else. And scsh is still beta. There are lots of POSIX stuff still needed to be added. You can help although. And personally, I stick with low level stuff as much as possible, for every byte of redundancy.
This! Rather than using a shitty bloated shell with half-assed programming features tacked on, just use a nice simple programming language that works and a nice simple shell that works.
awk
You guys will like this: some guy wrote a minimal LISP interpretor in awk!
>>35
Someone once implemented a Lisp interpreter in brainfuck.
Name:
Anonymous2012-11-02 11:50
Guys, just use rc like all expert programmers do.
Name:
Anonymous2012-11-02 11:52
The problem is we sometimes have to deal with BASH no matter what.
Name:
Anonymous2012-11-02 13:09
>>37 https://code.google.com/p/zozotez/ ?
Not a very good Lisp interpreter, and not actually written in brainfuck. It's written in something called ``EBF'', and then compiled to brainfuck.
>>38
Or es or xs if you're stuck in the real world.
>>39
The only time I've ever had to deal with bash is stupid GNU configure scripts that have #!/bin/sh at the top and then use obvious bashisms, which break on any operating system that isn't batshit insane.