Unless you're actually trying to do a huge synthetic operation where info would choke, e.g. creating an archive while removing existing files. That one is stil

Unless you're actually trying to do a huge synthetic operation where info would choke, e.g. creating an archive while removing existing files. That one is still possible to undo, just slower and more expensive... Then there are fun ones like Windows update holding 20 GB of insufficient undo, mechanical or hardware failures induced by extra load, and how to decide where an operation ends.