Also: tools that insist on crapping on my shell environment, `.{bash,zsh}rc` or `.profile` -- I like SourceTree [0] (to unfairly call out just one example), an

Also: tools that insist on crapping on my shell environment, `.{bash,zsh}rc` or `.profile` -- I like SourceTree [0] (to unfairly call out just one example), and while I'm aware of alternatives, it's cross platform, available to me without $$ payment ... but it is convinced that it cannot work without adding a block of code to my shell config. @OrderlyTiamat mentions Python world Anaconda https://news.ycombinator.com/item?id=32706193 https://news.ycombinator.com/item?id=32706193 @acdna acknowledges the more general idea of namespace pollution but if I'm reading it right, doesn't think it's a security issue particular to HomeBrew https://news.ycombinator.com/item?id=32707109 https://news.ycombinator.com/item?id=32707109 I can agree that taking over a namespace in the $PATH adds cognitive load to security vigilance, but I can accept that this is standard POSIX reality... But I don't like it when tools add to my $PATH - and then edit my config files in addition to that. I happen to like the UNIX way of filesystem structure for configuration. Re-writing my configuration on program launch takes away that very UNIX strength of composable tools and text files. [0] SourceTree: a nice Git GUI with `.ssh` integration -- https://www.sourcetreeapp.com https://www.sourcetreeapp.com (the ssh keychain is still a problem for me but I've only been trying to fix it for 20 years, and yes I try the nice keychain CLI tool from drobbins and macOS keychain integration and stuffs)