> I think the "Save" button is one of those situations where it's an easy solution to what could be a very complex problem. In many instances, if you get rid of some of the "standard" ways of doing things, you're setting yourself up for a lot of extra work. That doesn't mean it shouldn't be done, it just mean that it's something you have to factor into the cost of developing the application, and whether the benefits of it outway the costs.

That's a very good point. Time and time again, Cooper presents an improvement that would take a lot of work to implement. In particular, his view that programs should memorize as much of the user's preferences and actions as possible. Naturally, he's totally unsympathetic to the poor bums who would have to code it up. :)

But with OOP, a lot of things can be done once and for all, and you never have to think about them again. For example, it seems to me that in many cases, a dropdown picklist should display items in most-recently-used order, rather than taking the easy approach of just alphabetizing. Naturally, this is harder to code, but if you do it right, you only have to think about it once.