A large part of this comes down to the venue. The early part of GitHub really exemplified the "move fast and break things" mentality. GitHub broke the softwar

A large part of this comes down to the venue. The early part of GitHub really exemplified the "move fast and break things" mentality. GitHub broke the software world's ability to grapple with bugs, both in affordances i.e. the tools that it exposes for managing them, and, it would seem, cognitively. The way that GitHub approached bug tracking is one of the most frustrating examples of throwing away all progress just to start over from scratch and ignore everything that came before. A majority of GitHub's users' first experience interacting with a bug tracker was probably on GitHub, so they never really knew any better. The rest seem to be experiencing some collective amnesia about how to effectively file and otherwise triage/manage bugs. Basically none of the issues ever stumbled upon start with a clear and anodyne set of steps to reproduce. Every "issue" is a conversation. (And this seems to be not only tolerated but encouraged. It's madness.) About half are support requests, maybe more. Even when GitHub is used "correctly" to file bona fide bugs, on the whole, project maintainers seem to treat it as a general intake area for everyone else to file issues, and the project authors themselves hardly use it as their own database for known bugs. They're all jotting down vague descriptions in a text file that stays on their local machine or something, who knows. The entire phenomenon and attitude has to be one of the top 5 most annoying things about software development in 2020.