Why does turning it off and on again work so often? Like what is happening in the internal guts of the machine that's different? Is it in the code?
Why does turning it off and on again work so often...
Sometimes shit gets fucked in the course of operations
The software is shit, it will be reloaded from it's most ideal starting state.
For the same reason sleeping seems to fix so many problems, the little demons inside the silicone get to rest when the machine is off.
nobody knows
Anything stored in volatile gets chucked, pointers reset, program reverted to init state.
because state
Dear ESLoid,
You cannot use "it" as the subject of a sentence before having already stated what "it" is. In this situation, you ought to have used the term "an electronic device" in place of "it." If you desire a more general approach, the term "something" would have sufficed. Anything would have been better than "it."
Sincerely,
A concerned Grammar Nazi
Shit code lead to memory leaks that accumulate with time and waste more and more resources.
Shit like palo alto OS can be running for 2 years without sweating
Soiboy
Tongue my anus.
Rarely, radiation randomly causes bits in ram to switch states, but the software doesn't notice, so anything stemming from that flipped bit is going to be fucked.
Restarting the whole thing wipes the ram, and with it the erroneous bit.
Global variables get reset
Dear autist,
When someone uses a word ambiguously you can often infer context if you are non-autistic.
Sincerely,
Someone capable of infering things
it just do
Software is shit, clears that out. Hardware is susceptible to static. Power cycling clears that out.
/thread
Each period of being 'on' is like a little lifetime for the PC. As it ages it builds up a collection of diseases, physical ailments, and mental illnesses. Turning it off and on is like murdering it and replacing it with a fresh new clone baby of itself.
just like you and I, the ghost in the machine needs sleep too
Thank you for your service.
Stop contributing to the decline of the English language.
Memory leaks, badly designed drivers...
Most tests a program go thru are from the initalization point, not many tests are done after hours of the program running because takes hours to get to that point.
stateful shit
the source of all evil
This.
Functional programming wins yet again.