Does stackexchange forbid questions where there's an element of opinion, because the system's set up only for questions with "one right answer"? That seems awfully restrictive in the name of a system limitation.
Especially as, as 4ad observed, the asker chooses an incorrect answer annoyingly often -- so the "best answer" isn't always actually the best. As such, it's advisable to at least flick through the other answers anyway, despite this rule.
That's not the problem on the sample question.
I see that as the issue - that there has to be one answer. It's a site that promotes the same issue that plagues reddit, the hunger for karma.
It also seems like they have a lot of help vampires as I see many questions where the correct answer doesn't have even a single upvote.
what are the best practices when it comes to PHP?
And are there recommended ways of tackling certain task?
And these are, I believe, ambiguous, vague and overly broad (not to mention subjective).
Also the third question, the one you quote, is actually a yes/no question that would be pointless to answer. So, assuming that's not the real question... what is? I believe it IS difficult to tell what is being asked here.
StackExchange is just not meant for discussion, I think. At last not as it is right now.
And the existence of the other questions is beside the point -- the title of the question is "Good examples of PHP code for an intermediate PHPer?", the body is merely exposition. I only quoted the equivalent question from the body because it had better grammar than the title.
The most recent example, in my case, was:
http://stackoverflow.com/questions/10166086/good-examples-of...
"Can anybody recommend some [PHP] programs for me to look at, that promote best practises, but are simple enough for me to understand?"
"closed as not a real question; It's difficult to tell what is being asked here. [no it's not] This question is ambiguous [nope], vague [no], incomplete [er, no], overly broad [no], or rhetorical [still no] and cannot be reasonably answered in its current form [no again]. See the FAQ for guidance on how to improve it [mmm, passive-agression]."
... er, WTF guys? Given the minefield that is trying to write good PHP, it's a very good question. A couple of good answers had, I note, already been given, which puts the lie to the mods' reasoning -- but they killed it off anyway, even though it was showing promise? Really?
Reeks of power-tripping or jobsworthy moderation to me.