why is shell so bad

who allowed this horrifying thing to flourish

Beware Cat Shirt $21.68

Rise, Grind, Banana Find Shirt $21.68

Beware Cat Shirt $21.68

  1. 2 months ago
    Anonymous

    It does it's job of gluing together random utilities perfectly.
    If you're trying to use it for more, you're using it wrong.

    • 2 months ago
      Anonymous

      It doesn't, it's inept in even the most basic of functions like that. Have you ever put a variable before an important directory on your system? Yeah have fun nuking it when the variable is undefined lmao

      • 2 months ago
        Anonymous

        skill issue

        • 2 months ago
          Anonymous

          It's not even a ragepost. Just a thing I saw on shellcheck and reflected on this homie.

      • 2 months ago
        Anonymous

        damn you're right, if only they had a flag you could turn on to throw an error if you used an undefined variable. They could call it set -u or something

      • 2 months ago
        Anonymous

        [ "$var" ] && echo $var defined && [ -d "$var/dir" ] && echo $var/dir exists

      • 2 months ago
        Anonymous

        use set -u you moronic Black person

    • 2 months ago
      Anonymous

      I do not trust anyone who thinks shell is "perfect" to write reliable shell code. No, not even simple glue. Use shellcheck

      • 2 months ago
        Anonymous

        I just checked all the scripts I've written on their website, and all of them returned "this script is fine" or "warning, this may be unintended behavior" but every time the behavior was intended.
        Seems perfect to me.

        • 2 months ago
          Anonymous

          In that case I'm curious why you think it's perfect, unquoted expansion alone is enough to disqualify it for me. Most shell scripts I read are broken in really stupid ways

          • 2 months ago
            Anonymous

            If you need a variable to be considered as multiple different space separated values, don't add quotes
            If you need a variable to be considered as a single value, then add quotes
            I'm sorry you were filtered by grouping and sets, I hope haskell and set theory went better for you.

  2. 2 months ago
    Anonymous

    This little shit is the only reason you have a working operating system

  3. 2 months ago
    Anonymous

    it's essentially unfixable because we're stuck with POSIX brain damage until the end of time
    still somehow less gay than powershell tho

  4. 2 months ago
    Anonymous

    From what I understand, the programmer was black, so we have to unconditionally worship it and pretend it's good, or wayar rayciss.

    • 2 months ago
      Anonymous

      you're thinking of bash's author

    • 2 months ago
      Anonymous

      >blames black guy for just sticking to POSIX standards
      Are poltards really that bad with computers?

      • 2 months ago
        Anonymous

        >blames black guy for just sticking to POSIX standards
        But he didn't, bash is full of stuff that isn't POSIX compliant.

        • 2 months ago
          Anonymous

          POSIX *compliant* you tard, that doesn't preclude additional features. Which in bash's case make shell scripting only mildly painful instead of excruciating.

          • 2 months ago
            Anonymous

            I do this to speedmog and brainmog other programmers.

          • 2 months ago
            Anonymous

            >POSIX *compliant* you tard, that doesn't preclude additional features.
            I never said it did, moron. The post I was replying to said bash 'sticks to POSIX standards'. Strictly speaking, that isn't true--there are bash-specific extensions. The fact that bash can also run POSIX-compliant shell scripts is not relevant to my point.

        • 2 months ago
          Anonymous

          See. This is what I said about bad shell programmers just being morons.

    • 2 months ago
      Anonymous

      Steve Bourne is a hwhite man.

  5. 2 months ago
    Anonymous

    Shell and Haskell are the best filters.
    If someone isn't a good at shell scripting, or isn't good at functional programming, you know you shouldn't take them seriously.

    • 2 months ago
      Anonymous

      being maldesigned ancient touch powder doesn't make it good
      shell is deceptive in that it's piss easy to do basic shit or so you think it is until you add one extra character to the input string and your ~ vanishes

    • 2 months ago
      Anonymous

      hehe that picture is funny

    • 2 months ago
      Anonymous

      >shell
      >designed to be useful
      >the point is to make it get out of the way when you're trying to use utilities
      >can look frick ugly to moderately ok

      >haskell
      >designed to be useless
      >avoids state (computers are state machines), avoids procedures (computers run sequences of commands in order), avoids being used (no jobs, few programmers, fewer programs)
      >can look frick ugly to pretty good

    • 2 months ago
      Anonymous

      i've primarily written in shell for so long that all of its quirks and flaws feel natural, and other programming languages are what feel off to me. funnily enough, though, as per i do find haskell really enjoyable. lisp too. fricked up autism languages are just a blast

  6. 2 months ago
    Anonymous

    Use rc

  7. 2 months ago
    Anonymous

    sh could do with go style backticks for "final destination" quoting of strings, since ` isn't used in English text
    i know it was the old command substitution syntax, but that sucked

  8. 2 months ago
    Anonymous

    Make something better

  9. 2 months ago
    Anonymous

    Even powershell is better than BASH and both are dogshit

  10. 2 months ago
    Anonymous

    Because of Worse is Better and the bazaar model. It's random people and companies adding the worst "features" they can think of with the least amount of design and coding effort possible and not caring what the other people and companies are doing. In other words, it's the Unix philosophy.

    as_nl='
    '
    export as_nl
    # Printing a long string crashes Solaris 7 /usr/bin/printf.
    as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
    as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
    as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
    # Prefer a ksh shell builtin over an external printf program on Solaris,
    # but without wasting forks for bash or zsh.
    if test -z "$BASH_VERSION$ZSH_VERSION"
    && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
    as_echo='print -r --'
    as_echo_n='print -rn --'
    elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
    as_echo='printf %sn'
    as_echo_n='printf %s'
    else
    if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
    as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
    as_echo_n='/usr/ucb/echo -n'
    else
    as_echo_body='eval expr "X$1" : "X\(.*\)"'
    as_echo_n_body='eval
    arg=$1;
    case $arg in #(
    *"$as_nl"*)
    expr "X$arg" : "X\(.*\)$as_nl";
    arg=`expr "X$arg" : ".*$as_nl\(.*\)"`;;
    esac;
    expr "X$arg" : "X\(.*\)" | tr -d "$as_nl"
    '
    export as_echo_n_body
    as_echo_n='sh -c $as_echo_n_body as_echo'
    fi
    export as_echo_body
    as_echo='sh -c $as_echo_body as_echo'
    fi

Comments are closed.