4 ms·
Looking back, I realize it's wrong to assert opinions as facts with no basis at all. I definitely shouldn't have said that when I don't work at Rockstar or know
by indeedmug 6y ago
Looking back, I realize it's wrong to assert opinions as facts with no basis at all. I definitely shouldn't have said that when I don't work at Rockstar or know anyone who does.
But I still think people are demonizing too much Rockstar and are trivializing the bug when it's far from obvious. In my opinion, there is a lot of hyperbole statements about this issue when it's more useful to think if your organization could or would catch bugs like this.
- rubicon33 6y agoOk, to be fair I am doing to same thing (asserting opinions without facts). I don't work at Rockstar so it's true I have no idea how this bug was handled. I just have a hard time believing they didn't know about the bug, and I also have a hard time believing they didn't understand that it was one of the chief complaints from their end users (a simple check of any forum or discussion group is all thats needed). So, I an only assume short of an actual explanation, that they intentionally sidelined a fix for this bug. Why, is anyone's guess. If you had to ask me, management put all devs onto money making tasks like new items and store support, and fixing quality of life bugs even ones as egregious as this one, was a low priority.