2 ms·
We seem to be heading back towards those days. The property that made this possible was that DOS had little "state" to save before going bye bye. And these da
by digi_owl 11y ago
We seem to be heading back towards those days.
The property that made this possible was that DOS had little "state" to save before going bye bye.
And these days you get much the same with ChromeOS.
Heck, was there not someone in the -sec community arguing that state was to be considered bad?
- JBiserkov 11y agoThere was a very funny video where the main character's Chrome book gets destroyed every few minutes and a new one is delivered and he just keeps on working.
- digi_owl 11y agohttps://www.youtube.com/watch?v=lm-Vnx58UYo https://www.youtube.com/watch?v=lm-Vnx58UYo Seeing that original browser only UI makes me nostalgic.
- woliveirajr 11y agoI don't if it is bad, but I think that it just means that some computation isn't being done in full, and that's why you have to tell it to finish. Explaining better: any program should have the information saved when you click it to save, or at some specific time. If I don't save, ok, no problem loosing it. But opening a word processor and then turning the computer off shouldn't make the processor crash, or go through some recovery, or complain about something.