@Sig - In my experience the site tree metaphor doesn't scale beyond simple brochureware. As soon as you have nodes that contain more than 20-30 pages, things get really cumbersome because you're dealing with a single all-inclusive list, and most of the real estate in that narrow panel has already been sold off to parent and peer nodes that you don't care about.
If you have a calendar located at /about-us/company/events, and you have 200 events in the database, it's a punishing experience for the client to go in and add an event, or update an existing one.
The list view mitigates these issues to some extent. There's still a lot of digging to do, but at least it all happens cleanly, one paginated section at a time without all the extra noise. Further, for updates, a client can simply sort the table by last updated, and bring those pages to the top.
A bit off-topic, but an ideal solution to this is to provide a "dashboard" API that would bring common tasks to the top of the CMS. IMO, for a company that uses the CMS mostly for event management, "Create an Event" should never be more than two clicks away, and the inherent problem with the site tree model is that it's just too focused on hierarchy rather than content.
@Ingo - Does the client side storage persist across sessions? I think that's my biggest gripe is that every time I log in, I get the site tree, and for a user like myself, or my clients, it's just a useless view. I'd be happy to take a crack at it either way. Entwine rocks my world.