3 ms·
Speaking of frequent rebooting, I always thought the lack of support for orthogonal persistent state, seamless application checkpointing and built-in dynamic so
by panic 11y ago
Speaking of frequent rebooting, I always thought the lack of support for orthogonal persistent state, seamless application checkpointing and built-in dynamic software upgrade facilities represented a failure in modern mainstream computing.
When a system is in a complex, poorly-tested state, problems often occur. Rebooting solves these problems by putting the system back to a simpler, more predictable state. With orthogonal persistent state, the system remains in the complex state across reboots, and these problems become much more difficult to solve.
As a user, I agree that persistence is really nice, but I think we need to address the existence of these complex, poorly-tested states before we start transparently persisting them.
- Animats 11y agoThe only reason the Web works with such crappy coding is that the browser/server relationship is almost stateless. As new web technologies maintain more persistent connections, expect advice along the lines of "close the tab for the site and reopen it". Except sometimes you'll have to exit the browser completely (can you do that with IE?) to clear the connection.
- digi_owl 11y agoAnd this is why perhaps the old microcomputers were perhaps more user friendly than the modern PC. This because they were for the most part single task, and usually had a full reboot done before a new task was initiated.