3 ms·
Sadly, users usually reboot because some poorly written piece of software (probably written in C/C++ or Java) is out of wack and resetting RAM is the only way t
by transfire 4y ago
Sadly, users usually reboot because some poorly written piece of software (probably written in C/C++ or Java) is out of wack and resetting RAM is the only way to fix it.
Also keeping RAM running all the time would eat electricity and generate heat.
But I like the general idea. It definitely would be a good option.
- MichaelMoser123 4y ago> users usually reboot because some poorly written piece of software You can have that in Java - in any runtime environment, if your java processes keep consuming too much memory - swapping starts, on linux you will have the OOM killer, in the end the thing will reboot. Also operating systems can have bugs, hardware has bugs, nobody is perfect. > Also keeping RAM running all the time would eat electricity and generate heat. In a server room you wouldn't turn out the lights, ever.
- imtringued 4y agoHonestly people reboot not because something is poorly written, they reboot because it is too difficult to understand how to solve the problem so they go with the short term solution instead
- fuckstick 4y ago> out of wack and resetting RAM is the only way to fix it. This is not how this works. It doesn’t matter what language an application is written in, if a process is terminated, that frees all RAM consumed on any commonly used operating system.