![]() |
| https://x.com/i/grok/share/2ea0bd49206048f9b6aaab4c73a9a268 |
This is a wild bold statement. I'm going to propose that the Fibonacci sequence is an invalid entity in the real world. That is, everything about it is imaginary. And that mathematics is very seriously flawed. And that we all know it yet no one is permitted to discuss it.
- The number 0 is nothing
- The number 1 is everything
- All numbers above 1 are imaginary numbers, which do not really exist in the world, but do have utility when used for calculating things within this imaginary world we have created
- The Fibonacci sequence is an invalid entity in the real world because the program has to start from 2 and 0 an 1 both need to be hacked manually. Everything about Fibonaci is imaginary but we used it daily to improve utility
I'm also not sure that 0 is a valid number - having only 2 proper numbers in the world looks to me like a duality and I do not like dualities. But that's my beliefs leading me so I must be careful.
This dawned on me while playing around with assembler on my arm Macbook to see how all that worked using Grok to help. I used the classic Fibonacci sequence as subject matter for the small assembler program.
What triggered me, and it triggers me each time I play with it, is that a computer machine cannot calculate the Fibonacci sequence without needing to hack the first two numbers. That is, the program can only be made to work if the first two numbers are printed out freehand before moving onto the rest of the numbers which can be calculated manually.
So why can a computer, which is a mathematical logic machine using binary, not compute the whole sequence from 0 up?
I'm no mathematician, please put me straight on this. Tell me why?
If you can't tell me why then something is very wrong at the base of mathematical understanding and has been so for centuries.
I don't believe this is a good or a bad thing per se. No one will be harmed directly and immediately by it if true. But it might be contributing to the continuous problems the world has always faced - we are imagining what the world is really like, rather than looking directly at what is right there, in front of our faces.
*NOTE: do not worry about the unsigned overflow handling in the actual program, this is just an artefact I was trying to solve which brought me here. It has no bearing on the underlying problem and is just an effect of maxing out a 64 bit system and signalling overflow with the Carry flag. It would be identical in 32 or 16 bit system.
