zlacker

[return to "The largest number representable in 64 bits"]
1. 4death+ay6[view] [source] 2023-11-27 22:39:05
>>tromp+(OP)
The problem, as stated, provably has no answer. Assume such a number exists. Call it n. Now define a new 64-bit numbering scheme such that each number x is interpreted as n+x. n+x > n, which invalidates the hypothesis. There needs to be more constraints for this to be interesting. Like largest number representable where the representation is closed under addition and multiplication, or something like that.
◧◩
2. tromp+4C7[view] [source] 2023-11-28 08:22:26
>>4death+ay6
> There needs to be more constraints for this to be interesting.

Scott Aaronson's quote in the article provides this constraint:

> Precisely because the Turing machine model is so ancient and fixed, whatever emergent behavior we find in the Busy Beaver game, there can be no suspicion that we “cheated” by changing the model until we got the results we wanted.

Your "each number x is interpreted as n+x" is a clear example of the cheating that makes for an uninteresting scheme.

◧◩◪
3. 4death+lY7[view] [source] 2023-11-28 12:22:23
>>tromp+4C7
That doesn’t provide a constraint. The quote you mentioned is about why to model computation as a Turing machine vs. some other model, not about how to “find the largest number representable in 64-bits”, which doesn't have an answer.
◧◩◪◨
4. volemo+M38[view] [source] 2023-11-28 13:09:08
>>4death+lY7
I believe tromp implies a constraint of “existed before we started answering the question”.
[go to top]