It's seems that what the author has against responding publicly is that he cannot control himself when someone posts a bad review. If you can't do that, then do

It's seems that what the author has against responding publicly is that he cannot control himself when someone posts a bad review. If you can't do that, then do not respond, it's as simply as that. The rest of us, who want to read discussions between users and developers, and see how developers care about the problems would like to see public responses. In fact, I think the developers could greatly benefit from public responses by doing PR and by explaining that some bugs have already been fixed or that they are going to be fixed in the next version. Or by explaining that some problem is due to user configuration or at least post a workaround publicly in the store. Don't get me wrong, some ideas from the post are great. Like upvoting and downvoting, somewhat like many other e-commerce sites that have "Was this answer heplful?". But that doesn't mean that having public responses is a bad idea. Maybe he's not good are answering questions, but the rest of the developers would like to do so. So, no, the lack of a feature is not a feature.