Colin is talking about criticising implementation decisions in software, in particular unconstructive criticism bereft of context.

Colin is criticising your idea, but is also trying to understand how you formed that idea in the first place, in an effort to hedge against the possibility it has good reasons he can't see. He's not just saying, "your idea is garbage".

This comment was flagged dead, and I have vouched for it. Please don't downvote it ... it clearly shows an underlying misunderstanding, and as such deserves to be answered.

My comment that you reference was an attempt to find the merit in the idea that I couldn't see, but I assumed would be there because I was assuming the proposer thought it was a good one. I was starting from a position of "Well, this person thinks it's a good idea, but I can't see why, so let's see if we can find how it would work, and what problems it solves. Then we can address any potential drawbacks."

It was intended to be an invitation to get some discussion about how it would work, what it would do, what problems it would solve, and where the value lay. I was surprised and disappointed that no reply was forthcoming, and the thread died.

I guess I just wasn't clear enough, and for that I am saddened.

I liked the reply you posted, I'd be happy for getting such feedback / replies. And I think your reply can be edited a little bit, to start in a little bit more positive tone,

by changing from this:

> There are many, many problems with the idea, ...

to instead:

> I can see problems with the idea, ...

Nope. I think it's better to start with, This is interesting. then the questions. if you really see problems, state them. lead with engagement not criticism.

Maybe if you had said exactly what now you say your intent was, it would have been clear.