3 ms·
Yes, Google wave incorporated that as part of it's platform which would be cool for building Google Wave apps since it's already baked in. For other programs th
by crizCraig 16y ago
Yes, Google wave incorporated that as part of it's platform which would be cool for building Google Wave apps since it's already baked in. For other programs though, it seems like it would just be a matter of persisting the undo data. This data could also be source controlled allowing you to peer into the process of developers before you and gain a better understanding of the code. Keeping all your history in Photoshop would also be awesome. I wonder why apps don't do that more often. It seems like such an obvious and kick-ass feature.
- benatkin 16y agoIt's a complexity problem, though: not just for developers but for users. That's why it isn't about "other programs". The way out of apps dealing with complexity individually is for the platform to do more. This is what The Human Interface argues, going so far as to say there shouldn't be a plethora of separate apps for different tasks. When Google Wave first came out, Google touted its ability to be used all over the web, and to support custom-coded plugins that would get its versioning support for free. There are tradeoffs to adopting a front-end platform that gives useful stuff that are consistent across apps or sites for free. It's a very interesting concept to me nonetheless.