Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Recovery-oriented computing
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==System-wide undo support== {{seealso|Non-destructive editing}} The ability to [[undo]] across different programs and time frames is necessary in this type of system because human error is the cause of about half of system failures.<ref>{{cite web |last1=Brown |first1=Aaron |title=Addressing Human Error with Undo |url=http://roc.cs.berkeley.edu/talks/pdf/undo.pdf |publisher=ROC Retreat |accessdate=24 February 2020 |ref=human_error |date=June 2001}}</ref> Not having undo support also limits testing aspects of a production system because it doesnโt allow for [[trial and error]]. System-wide undo support should cover all aspects of the system. This includes hardware and software upgrades, configuration as well as application management. There are obviously limits to what can be undone, and these limits are currently being explored, tested and rated based on their tradeoffs.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)