sbach2o -> RE: research crash program doesn't stop (5/4/2010 2:39:11 PM)
|
I wouldn't be too fatalistic over issues going unanswered. There are many duplicates. There are lots of things that may be more of the 'wishlist' kind which probably is for later. Other stuff may need verification when its unclear whether there is an actual issue or a misunderstanding about game mechanics. Or someone might be reporting from an old version (me, when I dare to). The occasional seemingly old issue cropping up, stemming from an incomplete fix, may look like something like this. Then it is a lot of work to just take in everything. Acknowledging all issues, even if it is too early for them to handle them yet, may be too much. What with all the explaining, apologizing and getting involved into fruitless discussion this can lead to, over things they might have to sort out with themselves first. That doesn't mean the feedback couldn't be better. But any developer should be extremely cautious about publishing anything like, e.g. to-do lists. These things are non-committal until actual work has started, but would be mistaken as promises by (part of) the public. So I think the feedback we are getting is actually okay.
|
|
|
|