This approach is too simplistic to be useful in a multi-user environment.<p>Adds, changes, and deletes MUST be done immediately and cannot be queued without bottlenecking the entire system.<p>Undo's MUST be examined for every possible ramification. What if you change something and then want to undo it AFTER someone else has changed it again? What if you want to undo an add after someone else has already changed it? What about undoing a delete after someone else has added it anew? <p>Also, distinction must be made on how to handle a client side undo (simple) versus a server side undo (could be complex).<p>I agree with the writer that undo is a necessity, not a luxury, in a serious web app. For industrial strength apps, however, more thought is needed than what this writer has provided.
I recall this being lambasted on Reddit a while back:<p><a href="http://programming.reddit.com/info/2piup/comments" rel="nofollow">http://programming.reddit.com/info/2piup/comments</a>