- I posted about Paradox soliciting more feedback on the implementation of features.
- Daelyn75 agrees. He thinks a company called Stardock does this well.
- You reply that Paradox can't do this because they would end up breaking promises, completely missing our point.
- Daelyn75 gives examples of two companies that broke promises, and explains why that is not what we are talking about - Stardock solicits user feedback on feature implementation without breaking promises or making them.
- Your reply seems to indicate that you do get what the original point was (then why say you don't follow?), and you basically say that Paradox would gain nothing from the debate that would ensue from solicitation of user opinion on implementation, or that the solicitation itself would piss-off those who didn't get their way.
Well, I have to disagree... I've explained why it might be of great use, and Daelyn75 gives an example of a company that does it just right. Everybody would gain from this.
I'm not quite certain of what you're so afraid of. Your reasons seem to be half-hazard or almost satirical at best (we gain nothing from debate! it's dangerous!).
Edit: Re-reading your post, you do make one good, if perhaps unwarranted point: design-by-committee is bad. I agree, but I don't think anybody wants or expects that. The purpose is not to have Paradox go Soviet on us. They're great at using their user-base on every phase but this particular one, that's all. There are plenty of good implementation ideas that probably go un-voiced, only to be posted after it is too late.
Ok for starters ease up a little bit. We're having a civil discussion here. Calling my arguments satirical and trying to portray me as a free speech hater isn't helping matters.
Now to explain:
A). I did not miss the point in my first post. It was not the argument on feature implementation feedback I was reacting to, but rather the tone of
Daelyn75's post I quoted, which I felt was overly dismissive of what Paradox is already doing. Now I could certainly have misread his intent and attitude, but at the time that is how I personally felt reading it.
Therefore, my response was about showing Paradox more recognition about what they are already doing, regardless of what each of us feels should be offered in addition.
(Facing backlash from broken promises was really a minor part of my post and I don't see why you chose to focus on it.)
B). "I don't follow": By that, I meant quite literally that I had difficulty understanding the actual text of
Daelyn75's second response, its structure and the arguments within. Evidently, as your own words testify, I did in fact understand correctly, but when I made my post, I wasn't sure of it. Hence "I don't follow" to indicate, that I may have misread what he was trying to say.
My intention here was to avoid a misunderstanding.
C). As to your actual argument on implementation feedback, I don't really have a strong opinion. This is evidenced by the fact that my first comment on the matter was only a postscript. Since you have chosen to portray me as an anti-debate anti-feedback lobbyist I feel I need to clarify here: My arguments were on the possible reasons Paradox might have chosen not to provide such information to the fanbase.
My personal opinion on the matter is, quite simply, that if Paradox feels they could make such feedback work, that would be nice. If not I won't miss it.
I do hope I have clarified my opinion here and rectified any misunderstandings.
edit:
Why is this discussion taking place in a dev diary thread to begin with? This thread is about discussing the features introduced in this specific diary. Discussing Paradox's public relations policy in general, would, imho, be better served by opening a new thread on the matter.