EDIT: I don’t like the term ‘soy boy’, just picked ‘soydev’ for a lack of a better word, intending to use it semi-ironically.
recently I saw a project move PR discussions to discord, like what’s the point of using a git forge at this point, you can as well just use git send-email
I’m old enough to remember years of people complaining about overzealousness in closing threads as duplicate on forums, even when the issue might have been somewhat specific but the user could have just been unable to correctly recognize all factors at play with their issue (things like firewall, dependency versions and their configuration, environmental variables, hardware etc.) or the issue was actually caused by new bugs or API/ABI changes.
But at least there was some redundancy reduction and things were usually well categorized and tagged and many places actually implemented some pretty decent fuzzy search for similar existing issues. Instead we’ve ended up in both users and maintainers really wasting their time on something already resolved much more often.
If you don’t have time/are too stubborn for that, good luck skimming through tutorials to extract the info you need and pasting/adapting others’ code all while hoping there were no breaking changes since the snippets you want to use were published. At which point you might as well go ahead and browse type definitions and function signatures if you’re lucky to use something written in a self-documenting style.