Perhaps in the first case the question you asked was too broad compared to the standard expected for SO questions? Or too precise to be of use to anyone else?
The question was pretty broad but I think discussing it would have been very valuable for quite a few people. What bothered me were the snide responses. At minimum they should have stayed quiet or explained that SO doesn't deal with this kind of question.
Ironically most of the more helpful SO google results are helpful exactly because of the discussion/updates that took place in the comment chain under an answer from ten years earlier.
> Guys how do I filter an array in JavaScript?!
>> Use XYZ
>>> XYZ works, but it doesn't work in IE5
>>>> If you're on IE10 or above you can use ABC instead of XYZ, it is cleaner!
>>>>> Hey guys, change this {} to this {}, makes it faster on mobile!
Ideally, those 'discussions' would be incorporated into an answer, if only a new answer. Even-more-ideally, a single (most-upvoted) answer would incorporate all of the info from other answers and subsequent comments. That, of course, doesn't happen that often.
Every Wikipedia article has a talk page. But that doesn't mean that the purpose of the site is discussion. I think the same thing applies to SO.
If SO not for discussion is there a forum where you can discuss broad software architecture? Something with a spirit like HN where not everything is on topic but usually discussions are respectful and interesting.
That site is still not for discussions. It is however a site for Q&A on the software development process and architecture which tends to softer questions.