Don't tell me what my browser can't do

Re:Don't tell me what my browser can't do by sp332 on Saturday January 16, 2016 @02:38PM (#10916490)

I mean if the program requires too much RAM then it will either crash & stop or glitch and run forever, but you can always tell which way it will break :)

[ Parent | on HN ]

Re:Don't tell me what my browser can't do by paulddraper on Sunday January 17, 2016 @10:44AM (#10919750)

And how do you tell (without running forever)?

[ Parent | on HN ]

Re:Don't tell me what my browser can't do by sp332 on Sunday January 17, 2016 @03:23PM (#10920870)

You run the program for 2^(bits of state) steps. If it's still running, it will never stop because it must have repeated a state at least once. That means it's in a loop. So it takes a long time, but not an uncomputably long time.

By bits of state, I only mean the bits that the program is allowed to change. It doesn't necessarily include OS code or initialization code, as long as they are immutable while the program is running.

[ Parent | on HN ]

Re:Don't tell me what my browser can't do by paulddraper on Monday January 18, 2016 @05:54PM (#10927621)

Ah, yep, you're right.

Finite state -> solved halting problem

[ Parent | on HN ]