Chess.com stopped working on 32bit iPads because 2^31 games have been played
1–10 of 338 posts
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#2Real world example of why Apple is killing 32 bit apps on iOS.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#3How many other examples like this have occurred throughout computing history?
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#4"This was obviously an unforeseen bug that was nearly impossible to anticipate..."
Snarky... Except that there were probably years of games to notice that you were approaching a "magic number" like 2^31.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#5Whats why kids you should use cryptic identifiers.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#6were they ever expecting negative number of games? why signed integer?
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#7Real world example of why Apple is killing 32 bit apps on iOS.
This has nothing to do with CPU architecture.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#8Self-confidence as a programmer is when starting a new project, storing the transaction ID as a long rather than an int...
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#9were they ever expecting negative number of games? why signed integer?
It's very reasonable. This way they overflow into invalid values instead of zero.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#10This reminds me YouTube changed its view counter from 32-bit integers to 64-bit integers due to the popularity of 'Gangnam style' https://www.wired.com/2014/12/gangnam-style-youtube-math/