The Scoop GCC manifest (and everything that depends on it) has been broken since January. GCC for Windows is now distributed using an unsupported archive format, and development to support that format has stalled out.
https://github.com/ScoopInstaller/Main/issues/1752
One of the maintainers seems to be forking the scoop client, but their fork still uses the unmaintained main package bucket.
https://github.com/Ash258/Scoop-Core
I'm pretty unhappy with the behavior of the maintainers to the author, though. There are better ways to suggest issues with documentation than just "this is a lie", and better ways to say a function name could be better than "is a horrible name". I also think it's rude to ask for a patch to be completely rewritten and then ignore it after the author does so.
The maintainer you are referring to isn't one of the original maintainers. It looks like they are missing in action, but for what it is worth, I never saw them respond in this way.
Looks like a frustrating choice between a polite maintainer that isn't around or a rude maintainer that is still active.
Ash258 is not one of the official maintainers, but he's a very active member of the community (more active than the actual maintainers), commenting on most PRs to official buckets and maintaining his own bucket https://github.com/Ash258/Scoop-Ash258 as well as a Scoop fork https://github.com/Ash258/Scoop-Ash258 with many improvements and issue fixes over the upstream. He also mods the Scoop Discord server.
However, his comments are often harsh, like you noticed. He's mostly on-point, but is very quick to rudely shoot down anything he disagrees with. Also he bans discussing or even mentioning his fork of Scoop on the Discord server, which is super weird since he put it publicly on GitHub in the first place.
Interesting. I haven't had any issues with scoop in a long time and the manifests continue to be updated, so I had not even realized the original maintainers had gone quiet. It would be a true shame if this project decays without a successor or official word from the maintainers.
Scoop is maintained, but just... really slowly. It's a shame. For example it took more than a month and two maintainer pings to merge an absolutely trivial PR to add Python 3.8 (a single character change over the Python 3.7 manifest): https://github.com/ScoopInstaller/Versions/pull/226
For the most part, this does not matter. Most of the existing stuff is already present in buckets and auto-updated by CI. The problem is just when something breaks or something new needs to be added, which can take a non-deterministic amount of time.
Also Scoops makes it super easy to add 3rd party buckets and even install stand-alone manifests published on a HTTP URL (so even update is working). If you really need something that has a PR but is not merged yet, you can install directly from the PR and just change the source once it's merged, which is just a small hassle.
The Scoop GCC manifest (and everything that depends on it) has been broken since January. GCC for Windows is now distributed using an unsupported archive format, and development to support that format has stalled out. https://github.com/ScoopInstaller/Main/issues/1752
Someone made a workaround patch using a different GCC mirror, but it's been sitting open for a month. https://github.com/ScoopInstaller/Main/pull/1933
One of the maintainers seems to be forking the scoop client, but their fork still uses the unmaintained main package bucket. https://github.com/Ash258/Scoop-Core