• rozodru@piefed.world
    link
    fedilink
    English
    arrow-up
    34
    ·
    4 days ago

    yeah I remember a year ago when they said the same. They keep moving the goal posts because they HOPE it’ll happen, but it’s not going to. LLM’s across the board, regardless of the company, have progressively become worse. They’ve sunk billions into something that simply isn’t improving and they either don’t know how to improve it or are just praying to whatever gods they believe in that it will some how magically get good.

    There’s nothing left to feed these things. For example you can go to Claude right now and ask it something so painfully simple that there’s a strong chance it’ll hallucinate a solution. not even a strong chance, a guaranteed chance. Like I just asked it “With the Fish Shell how can I get cat <<EOF > notes.txt to work?” it didn’t know how. it presented 3 options all of which were wrong. It claimed I was using an older version of Fish that doesn’t support Heredocs. that’s not true. Fish doesn’t support Heredocs at all, period, and never has.

    • oktoberpaard@piefed.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 days ago

      I agree that comments like this are just hype. However, this is what Claude responded first try when I asked it your question verbatim:

      Fish doesn’t support the <<EOF heredoc syntax — that’s a Bash/POSIX feature. Here are your options in Fish: Use printf or echo:

      printf '%s\n' \
        'line 1' \
        'line 2' \
        'line 3' > notes.txt
      

      Use begin/end with a string:

      echo "line 1
      line 2
      line 3" > notes.txt
      

      Use string with multiline input:

      string collect -- "line 1
      line 2
      line 3" > notes.txt
      

      Or just call bash inline for a one-off heredoc:

      bash -c 'cat <<EOF > notes.txt
      line 1
      line 2
      line 3
      EOF'
      

      The printf approach is generally the most idiomatic Fish way to do it.​​​​​​​​​​​​​​​​