@code_star Hahahaha nice
You think I’m joking?
A research engineer's post points out that searches for the Bash safety idiom set -euo pipefail stayed near zero for years before rising sharply after 2020, lining up with the period when large language models began routinely emitting shell scripts that include those exact flags.
@code_star Hahahaha nice
You think I’m joking?
The timing suggests developers are now encountering the command through model outputs rather than earlier documentation or training, though the data shows only correlation without confirming prior awareness levels.
No training-corpus analysis or developer surveys back the claim that the command was unknown before LLMs, leaving room for alternative explanations like broader DevOps tooling changes.
No Digg Deeper questions have been answered for this story yet.
Another thought here (and man I feel old saying this).
Is that people tended to solve the problem this solves in the language they were most comfortable with in the past.
Yes, I have read the replies, and I’m very happy for you people that wrote lots of bash.
I don’t think it’s out of line, to say unless you worked on infrastructure, or were a strange hardcore Linux guy, you probably didn’t do all that crazy of bash other than what you new for scooting around the terminal. You could just use like .. a real language for reliability.
Also, if you were a REAL Linux nerd you probably were dabbling with something like fish instead of bash before 2020 and only switched back to zsh/bash because there were no docker images setup for fish and wasn’t going to work with GPUs.
What’s funny about this, is it’s not evidence no one knew the command before this.
It’s just a marker of when that exact set of flags, in that order, made it into someone’s post-training dataset.