parthenon VS discussions

And the library/bundle part is https://github.com/getparthenon/parthenon

True, though shallow clones have performance issues: https://github.com/Homebrew/discussions/discussions/225

And the reply was "command not found". Researching the error, I found that I need to "Add Homebrew to your PATH in ~/.zprofile:"

Seems like this user fixed itusing gcc-12 instead of 11 https://github.com/Homebrew/discussions/discussions/3490

Specifically Neovim is in homebrew/core if brew doctor mentions a probelm with homebrew core you need to fix it. See this issue: https://github.com/Homebrew/discussions/discussions/1512

His fictional story reminds me of the Homebrew 2.7 debacle: https://github.com/Homebrew/discussions/discussions/340

TL;DR: They deprecated "brew cask install" in version 2.6, then removed it in version 2.7. Sounds fine, right? Except version 2.6 was released on December 1st, and 2.7 was released 20 days later on December 21st, breaking everyone's scripts just before the holidays.

I agree with the overall premise, but there's a balance to be had somewhere. When millions of developers use your tools, you do have to be a little more careful when you make breaking changes.

I think Linus has a point here with his "don't break userspace" rule.

https://github.com/Homebrew/discussions/discussions/3490 it says to get gcc-12 ... but macos is not my wheelhouse

It's a bit of history:

https://github.com/Homebrew/discussions/discussions/225

https://stackoverflow.com/questions/6941889/is-it-safe-to-sh...

https://stackoverflow.com/questions/6900103/why-cant-i-push-...

Modern git appears to have implemented solutions to these limitations, but old habits die hard.