Real world example of why Apple is killing 32 bit apps on iOS.
This has nothing to do with CPU architecture.
Chess.com stopped working on 32bit iPads because 2^31 games have been played
31–40 of 338 posts
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#32Real 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
#33"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
#34It's fascinating... the Y2K problem never came to fruition because - arguably - of the immense effort put in behind the scenes by people who understood what might have happened if they hadn't. The end result has been that the entire class of problems is overlooked, because people see it as having been a fuss over nothing. I sometimes think it would've been better if a few things had visibly failed in January 2000.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#35Self-confidence as a programmer is when starting a new project, storing the transaction ID as a long rather than an int...
Or UUID...
The simplest way to do that is to just throw UUID at all problems from the start. (https://github.com/alizain/ulid s are better, but there aren't libraries to generate them in literally every language + RDBMS.)
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#36It's fascinating... the Y2K problem never came to fruition because - arguably - of the immense effort put in behind the scenes by people who understood what might have happened if they hadn't. The end result has been that the entire class of problems is overlooked, because people see it as having been a fuss over nothing. I sometimes think it would've been better if a few things had visibly failed in January 2000.
Having to spend billions of dollars on programmers' goofy means of saving a few bytes of memory is a pretty visible failure.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#37That was a valuable lesson.
(I actually generated most entries myself while testing stuff - live in prod of course - and while there were probably fewer than 255 votes, the AUTO_INCREMENT did its job and produced an overflow).
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#38Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#39Do we know when chess.com launched? If so, we can calculate the average number of games being played per second.
Re: Chess.com stopped working on 32bit iPads because 2^31 games have been played
#40It's fascinating... the Y2K problem never came to fruition because - arguably - of the immense effort put in behind the scenes by people who understood what might have happened if they hadn't. The end result has been that the entire class of problems is overlooked, because people see it as having been a fuss over nothing. I sometimes think it would've been better if a few things had visibly failed in January 2000.