Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by timewizard on Wednesday April 23, 2025 @08:43PM
(#43778253)
> If you promise randomization
You don't. You say the order is undefined.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by __float on Wednesday April 23, 2025 @11:07PM
(#43778928)
That isn't the point. In practice, if you provide randomness, it will be depended upon.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by psnehanshu on Wednesday April 23, 2025 @11:27PM
(#43779002)
Why is that? Is that just bad coding habits?
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by simonask on Thursday April 24, 2025 @02:37AM
(#43779871)
All of this is bad coding habits. That's why we're here.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by dwattttt on Wednesday April 23, 2025 @11:00PM
(#43778894)
You can randomly not randomise it :)
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by scott_w on Thursday April 24, 2025 @05:03AM
(#43780617)
Semi-related: this type of thing is actually covered in the Site Reliability Engineering book by Google. They highlighted a case of a system that outperformed its SLO, so people depended on it having 100% uptime. They "fixed" this by injecting errors to go closer to their SLA, forcing downstream engineers to deal with the fact that the dependent services would sometimes fail for no reason.
I know it's easier said than done everywhere, just found it to be an interesting parallel.
And then you can never remove it!