I've been learning and playing around with Views2 for a while now and have been wondering what use anyone would have for the default view other than the obvious.
The obvious: If you have a number of similar views you can save some time and work by inheriting most of the fields, filters, sorts, etc from a default view. Or you later make a change to one view that you want to propagate to other views without having to manually update each one.
Does it have a use beyond that? If so it's not at all obvious.
I'm willing to bet for the vast majority of users, the default view and the associated UI overhead and complexity of overriden values, is more of a nuisance than a help. In addition, anything in a group that is overriden makes all other items in that group overriden as well, so as soon as you do that a lot of the convenience of inheriting default values goes away (changes to other views that get saved to the default view cannot then be propagated to additional views). Most people have but a handful of views and manually building each one separately isn't that big a deal - it's done once and your finished.
So I would vote to either remove the default display altogether or at least allow the user to toggle its existence (along with the whole overriden overhead) on or off. Or maybe just replace the default concept with a clone concept since it's really done only once. That would get rid of the overriden complexity as well.