Topic: Application crashes are a social construct
+Anonymous A — 1.4 year ago #65,071
For instance, when a program is about to run out of memory, the OS could offer the user the option to terminate other background processes that are consuming significant resources rather than automatically terminating the prioritized one out of the blue with the highest RAM usage which is usually guaranteed to be currently in use by the user. And there should be checkpoints (automatic backups) which would allow any arbitrary program (even those without file saving options) to revert to a previous, functional state in case of a freeze, error or crash. This would minimize data loss (e.g. unsaved projects) and user frustration, making the software experience more seamless and reliable through recovery.
I think the problem lies on the fact that raw RAM data isn't made accessible to the end user due to privacy and/or security reasons.
·Anonymous A (OP) — 1.4 year ago, 3 minutes later[T] [B] #653,113
Imagine what kind of stuff could've been uploaded online that people have worked on for several hours that were lost forever due to a simple crash caused by a stupid bug (e.g. division by zero).
+Anonymous B — 1.4 year ago, 20 minutes later, 24 minutes after the original post[T] [B] #653,115
@previous (A)
You can divide by zero. Proof
On September 21, 1997, a division by zero error in the "Remote Data Base Manager" aboard USS Yorktown (CG-48) brought down all the machines on the network, causing the ship's propulsion system to fail.
+FuckAlms !vX8K53rFBI — 1.4 year ago, 11 minutes later, 36 minutes after the original post[T] [B] #653,117
You're not wrong.
+Chuffed !3qyf8DDj3w — 1.4 year ago, 3 hours later, 4 hours after the original post[T] [B] #653,124
We could start with forcing companies to not sell Chromebooks with 4 gigs of ram; same with Apple with only 8GB in 2024. It's not fit for their intended purpose!
Start a new topic to continue this conversation.
Or browse the latest topics.