One thing I miss most from Unix systems, in "personal" systems like Mac and PC, are the old hard shutdowns.
When you did shutdown, you could choose to give "other users" a minute or two to shut down, or just shutdown right now. On my own systems I just did "now." Even on systems I managed, as I had already shepherded all users off by that point.
And the systems would come down right now in a second or two, even with cached file systems (though, theoretically those could cause some delay, but usually caches were generally empty by this point).
But now we have microprocessors which are 1000 times more powerful than the original Unix minicomputers, and they struggle for minutes to shut down, frequently giving up because this or that process declined to accept the shutdown order.
Typically, such an application might have modified project work that the user hasn't written out yet.
In nearly all such cases, if I hadn't actually written something out, when I give a shutdown order, I didn't intend to.
I would be fine with going back to hard shutdowns. But if not, could it be some sort of preferences option? Or maybe a different kind of shutdown, slow vs fast, for example.
Or maybe somehow get all the things that want this or that state saved, to present all their demands more quickly, or even in some kind of integrated way, rather than having to wait for minutes for each different program to responde...why are they so slow in doing that?
When you did shutdown, you could choose to give "other users" a minute or two to shut down, or just shutdown right now. On my own systems I just did "now." Even on systems I managed, as I had already shepherded all users off by that point.
And the systems would come down right now in a second or two, even with cached file systems (though, theoretically those could cause some delay, but usually caches were generally empty by this point).
But now we have microprocessors which are 1000 times more powerful than the original Unix minicomputers, and they struggle for minutes to shut down, frequently giving up because this or that process declined to accept the shutdown order.
Typically, such an application might have modified project work that the user hasn't written out yet.
In nearly all such cases, if I hadn't actually written something out, when I give a shutdown order, I didn't intend to.
I would be fine with going back to hard shutdowns. But if not, could it be some sort of preferences option? Or maybe a different kind of shutdown, slow vs fast, for example.
Or maybe somehow get all the things that want this or that state saved, to present all their demands more quickly, or even in some kind of integrated way, rather than having to wait for minutes for each different program to responde...why are they so slow in doing that?
No comments:
Post a Comment