One step forward, two steps back.
First, in a reply to the post above me...no, they didn't fix the updating so you end up downloading all 20MB+ every time. Hooray!
I got it updated finally. For some reason it insisted on downloading some file but didn't ever tell me what it was and it never seemed to finish. I got Steam running under Wine on my netbook and updated it that way and just copied it back to the desktop and the problem went away. Never did figure out what it was trying to get.
I do like the new Downloads page. Tells you how big the update is, how much of it you've already downloaded, and an ETA on completion. However...there are still some problems:
1) The ETA calculation is completely broken. No, Steam, I can not download 200MB in under 15 minutes on my connection. How do they get it THIS wrong?
2) Pausing updates is still wonky, where it will continue downloading the last file it was working on until it is done. Probably not a big deal for most, but its really shitty for me. But I know why they do it...
3) No mid-file resuming. Yeah, now that it shows how much has been downloaded I've basically confirmed this.
So theres a 215MB update for Red Orchestra that I want to download. This is spread over 3 files according to the "Verify cache" thing, so there must be some substantial files to grab. I let it run to about 25MB, then "paused" it. When it didnt actually stop eating up my bandwidth, I closed Steam (and then killed the process because Steam will still run and try to get that file!). Next time I started it up it said I had 44MB downloaded, which just shows that yes, it kept downloading.
Now heres the fun bit. When I clicked "Resume", it dropped back to 15MB downloaded. Why? Well, the only reason I can come up with is it started over on the unfinished file. Steam does not support arbitrary pausing of file downloads and won't resume half-finished files. This is SUPER annoying. Just about every server on the internet supports this, why can't Steam?
So yeah, its nicer and it has improved, but underlying problems still remain. You'd think with a large UI update and now making a Mac client (and now rumors of Linux) that this would be the time to fix and improve this background shit.