perishthethought@piefed.social to memes@lemmy.worldEnglish · 29 天前Windows updatesi.imgflip.comimagemessage-square10fedilinkarrow-up1286arrow-down16
arrow-up1280arrow-down1imageWindows updatesi.imgflip.comperishthethought@piefed.social to memes@lemmy.worldEnglish · 29 天前message-square10fedilink
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up2arrow-down1·28 天前Beating turning the computer into a brick does not make it “the preferable way” to do it.
minus-squareConfused_Emus@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·28 天前Update fails, OS rolls back failed changes. What would you prefer it to do?
minus-squareKanda@reddthat.comlinkfedilinkarrow-up1·28 天前Boot into terminal and leave you staring at an empty prompt
minus-squareExcessShiv@lemmy.dbzer0.comlinkfedilinkarrow-up1·28 天前So in the event of a failed update, what would be the preferable way to handle it then? I think automatically rolling back to a functional state before the update is pretty optimal.
Beating turning the computer into a brick does not make it “the preferable way” to do it.
Update fails, OS rolls back failed changes. What would you prefer it to do?
Boot into terminal and leave you staring at an empty prompt
So in the event of a failed update, what would be the preferable way to handle it then? I think automatically rolling back to a functional state before the update is pretty optimal.