I contend five points:
1. Specifically: my question was put on hold but is directly relevant to WP development
A simple reality is that Wordpress is a CMS, not a framework. Therefore development within Wordpress entails more than just modifying or writing code - it also involves creation and formatting of content. My question was directly related to making the creation and formatting of content, easier/better. There is, conceptually speaking, no difference between asking how to extract a taxonomy term from a query, and how to highlight shortcode syntax in the editor. Both are related to development within Wordpress, and unless the title of this stack exchange means something OTHER than "Wordpress Development", differentiating between the two is illogical.
2. Generally: the use of plugins and extensions is inherently part of Wordpress development.
It's GOOD for the Wordpress ecosystem if developers aren't constantly re-inventing the wheel, and are using well established, tested, vetted, pre-built solutions to solve common problems.
- This keeps development costs down
- It keeps more eyeballs on potentially buggy code
- It improves the overall quality of sites built in Wordpress
- It helps provide some standardization to Wordpress development, which in turn...
- Allows a developer to interoperate between Wordpress projects more easily (e.g. a new hire that is already familiar with the Wordpress ecosystem can more easily jump into a project that has existing pre-built solutions)
- Is consistent with the spirit of open source development: many hands, one result.
Thus any knowledge shared regarding the Wordpress plugin ecosystem is good for the Wordpress development community as a whole. And similar to the above, extensions and plugins as solutions to problems are no different than answers related to the Wordpress Codex. Wordpress Codex is only ONE part of Wordpress development. Usage of its plugin ecosystem is another part. Both are equally important.
3. All answers are inherently opinionated
The text regarding the off topic nature of asking about plugins or extensions says this:
library or off-site resource is out of scope of the site, as it attracts opinionated answers and spam
There is more than one way to do just about everything in software, and there is no single right answer. Ask how to get the date one week from today in PHP, and you'll get 10 different, but equally valid answers - each based on someone's opinion as to what an appropriate solution would be.
Yes, there are lots of wrong answers, but there are many right answers as well. Wordpress is no exception. There are multiple ways to solve problems in Wordpress, and that includes problems which can be solved via usage of existing plugins. The ENTIRE POINT behind the answer voting system is to have crowd-sourced validating of someone's OPINION as to what the solution is. The concept of upvoting and downvoting answers is essentially moot if you are looking only for fact-based answers.
At the end of the day, people post answers which they may or may not support with facts or evidence. That is why we have voting. They are at least presenting some information and it is up to the asker, as well as viewers, whether they consider that information valid or not. The votes help them decide what other people think of that information so that they can make an informed judgement on the quality of the answer.
4. It's my bloody question, I will decide for myself how to handle the replies
Correct me if I'm wrong, but Stack Exchange is not an encyclopedia. It is a service whereby a person can ask a question specific to their needs, and get a tailored answer from those willing to help them. Being a service, that conceptually shifts the ownership mostly to the consumer of that service. Put rudely, you shouldn't be attempting to save me from my own question. If I am ok with opinionated answers, then that is mostly none of your business. Yes, my question does not exist in a bubble and does impact the question river. Some moderation is definitely needed. But it's still MY question, and I should be entitled to the opportunity to get an answer (this being a service and all).
5. GUIDANCE is as valuable as a concrete answer
If the fundamental point of this stack exchange is to aid in the development of Wordpress as its name implies, then answers which provide guidance are just as valuable as concrete answers. Therefore by extension, questions seeking guidance are just as valid as questions seeking concrete answers. If someone's answer has helped me, then it has helped me. End of. This exchange has done its job. And by extension, it has helped anyone else who has the same question.
Failing the above points, then I would recommend this Stack Exchange be renamed to something more specific than "Wordpress Development" (I'm not being flippant), as help with general Wordpress development inevitably must allow for questions which are presently beyond the scope of this exchange.