3 ms·

I understand your frustration, but anyone who's run (or been on) a dev team knows you have a million things you could/should be doing, and many, many priorities

by awill 6y ago

I understand your frustration, but anyone who's run (or been on) a dev team knows you have a million things you could/should be doing, and many, many priorities. Often supporting new launches/features is the priority. Sure, ideally there would be someone internal advocating for a fix like this on behalf of customers. But Shameful isn't the right word. It's a miss like any other.

shock-value 6y ago
The egg that's on Rockstar's face has more to do with how much money they likely left on the table by not diagnosing and fixing this issue early on. (And assuming they had a team overseeing this aspect of performance with adequate tools to observe and debug it should have been trivial.) I personally feel like the magnitude of this -- especially compared to how simple the solution is -- makes it a miss that's really much more extreme than most others. EDIT: Though I agree that "shameful" isn't the right word to use. Rockstar wronged themselves much more so than any other party.
SV_BubbleTime 6y ago
Obviously you are right... but... If the fix had been some super application specific super obscure thing, we would all understand. Instead... the bug is easily describable to anyone who knows what JSON is and the fix is “don’t parse JSON the slow way”. So I think some of the leniency afforded to the devs may be misplaced. Then again, hindsight and all that.
- thitcanh 6y ago
  The cause doesn’t actually matter much, usually one doesn’t know the issue until they investigate. So often issues remain open for lack of interest, then someone finally does and it’s a missing comma. This doesn’t affect the fact that the issue has been ignored. I’m sure GTA has unlimited bugs to look into, but a bug that turns people away before they even start should have probably been given higher priority.
  - deleted 6y ago
    [deleted]
- Dylan16807 6y ago
  > If the fix had been some super application specific super obscure thing, we would all understand. Would we? Even if I don't understand what it's doing, devs doing nothing about an O(n^2) algorithm that takes multiple minutes every load is clearly a big mistake. Even if it's something that has to be that slow, cache the result.
sellyme 6y ago
Oh absolutely, I have a whole host of stuff on my todo list for projects I'm developing that has been there for months and will remain there for months longer. That said, they're all things like "refactor the frobnicator code so it's more obvious what it does" and "make templating system log changes to server". Nothing on my list says "Look in to that major performance issue that literally thousands of customers complain about every single day". That stuff gets sorted immediately.

by awill 6y ago

shock-value 6y ago

The egg that's on Rockstar's face has more to do with how much money they likely left on the table by not diagnosing and fixing this issue early on. (And assuming they had a team overseeing this aspect of performance with adequate tools to observe and debug it should have been trivial.) I personally feel like the magnitude of this -- especially compared to how simple the solution is -- makes it a miss that's really much more extreme than most others. EDIT: Though I agree that "shameful" isn't the right word to use. Rockstar wronged themselves much more so than any other party.

SV_BubbleTime 6y ago

Obviously you are right... but... If the fix had been some super application specific super obscure thing, we would all understand. Instead... the bug is easily describable to anyone who knows what JSON is and the fix is “don’t parse JSON the slow way”. So I think some of the leniency afforded to the devs may be misplaced. Then again, hindsight and all that.

thitcanh 6y ago
The cause doesn’t actually matter much, usually one doesn’t know the issue until they investigate. So often issues remain open for lack of interest, then someone finally does and it’s a missing comma. This doesn’t affect the fact that the issue has been ignored. I’m sure GTA has unlimited bugs to look into, but a bug that turns people away before they even start should have probably been given higher priority.
- deleted 6y ago
  [deleted]
Dylan16807 6y ago
> If the fix had been some super application specific super obscure thing, we would all understand. Would we? Even if I don't understand what it's doing, devs doing nothing about an O(n^2) algorithm that takes multiple minutes every load is clearly a big mistake. Even if it's something that has to be that slow, cache the result.

sellyme 6y ago

Oh absolutely, I have a whole host of stuff on my todo list for projects I'm developing that has been there for months and will remain there for months longer. That said, they're all things like "refactor the frobnicator code so it's more obvious what it does" and "make templating system log changes to server". Nothing on my list says "Look in to that major performance issue that literally thousands of customers complain about every single day". That stuff gets sorted immediately.