I think you may be misunderstanding GP's clarity around the intended scope of the project with a lack of enthusiasm about maintaining the project.

Homebrew is critical infrastructure, which is exactly why it shouldn't change dramatically.

Now, if GP has lost interest in the project, or doesn't have the time to keep it running satisfactorily, I'd definitely agree with you - but I didn't get that impression from his post.

If I understand correctly, it's not about losing interest but ensuring there is a successor for when GP wishes to step back or is forced to do so. The community should acknowledge this and fund training and possibly salary for who's next.

I’ve been working on finding a successor and ensuring the project has a bus factor of more than one for at least. The latter has been solved but the prior won’t until I step down, despite my best efforts otherwise.

Many times. I haven’t found one yet whom I felt would take over everything I do. Given I still enjoy it, it feels like there’s no need to reduce the number of humans working on the project in the hope that it’ll encourage someone else to step up and do more.

It's not critical infrastructure.

There are better alternatives, even, that are a quick and painless install process away. For example, nixpkgs is competitive with it, and does not include the Google phone-home supercookie tracking spyware that is on by default without consent in every Homebrew installation, and works great on macOS.

Homebrew could disappear tomorrow and nothing extremely bad would happen. That can't be said for the power grid or water system. Tossing around the term "critical infrastructure" for things that are important but very sub-critical is hyperbole that waters down the (important) term to meaninglessness.

I bumped into a lion in the forest the other day that was aghast and somehow offended and told me the same thing when I mentioned that power grids and water systems were critical infrastructure.