Yet another reason people might not report bugs is there can be an attitude of hostility towards reporting bugs by open source maintainers whose priorities don’

Yet another reason people might not report bugs is there can be an attitude of hostility towards reporting bugs by open source maintainers whose priorities don’t align with helping their users. It’s exceedingly common for open source maintainers to reply on bug threads with disingenuous reasons and mental gymnastics to avoid calling a bug a bug, and try to pass it off as an obscurely defined feature request or grumble that whatever use case is hitting the bug “shouldn’t” be supported or would require structural changes to the design (which is what caused the bug) that make it the user’s fault for wanting something that would require scrambling someone else’s arbitrary design choices. A big example from my recent memory is bugs with various cloud storage APIs that result from blob storage not behaving like a real file system, but user semantics still relying on path delimiters that group things into a hierarchy of directories. People get disinfranchised because you’ll be given some parochial, nonsense dismissal saying that the backend being undifferentiated blobs somehow means the user shouldn’t rely on filesystem-like abstractions, instead of the library maintainers just doing the work and adding indexing and making the API functions automatically deal with delimiters & key prefixes so that it “just works” like a set of folders to the user (who doesn’t and shouldn’t care about an unrelated implementation detail like blob storage). This is just an example, but illustrates a wider point. You often feel like what’s the point of reporting this bug? I’ll just be given some empty dismissive answer about how it won’t get solved and I should philosophically refactor my entire use case from first principles so as to not need what I need.