This line of thinking is something you will quickly be disabused of once you try supporting software that hundreds of millions of people use.
And I say this as someone that loves the Unix philosophy dearly.
How, exactly, would the proposed solution (combined with a setting to disable it) break, and how would implementing it the way Anthropic did address that? Be specific.
I've never heard of the 'move fast, break things' mentality ever giving a damn about number of users. If so, no changes would ever be made. The great thing about having millions of users is QA can be eliminated entirely as you'll start hearing about issues from the users directly.
Frontier lab AI agent tools break their users’ workflows worse than this on a regular basis.
Bash does this well, reading only the first of half a dozen config file locations it searches. And if the user needs it to read from an additional location, just add a source line to that location.
> This line of thinking is something you will quickly be disabused of once you try supporting software that hundreds of millions of people use.
> And I say this as someone that loves the Unix philosophy dearly.
Unix way would be just to tell users to `ln -s` and stop bothering with this.