Sandvox - the new GUI editor for websites, which was just introduced as a beta by Karelia - is really nice in concept. It offers an overall view of the website - and that is on the components of the website. Nicely structured, so that you can easily make changes to pages. The whole thing is also really easy to use - with nice wizards and good integration with iLife. Publishing is not only to .Mac, like with iWeb, but for example via SFTP to a normal server.

And Sandvox sucks hamsters through straws.

Sorry, but you can't put it any nicer. The thing is a complete and total catastrophe in the present second beta. I didn't give it many tasks - I didn't get that far. I created a homepage, a page with a single image, and a photo album. None of that is particularly difficult. The photo album was given 39 images - directly taken from iPhoto. That's not complicated, one would think.

But the software just sucks up 1.5 GB of memory because of these images and reduces a Mac Mini to a crawling snail. With every click in the navigation in the software, you wait for 10 or 15 minutes until the selected page appears. The created file with the site is by the way only 280 KB in size - why it then occupies so much memory, I don't even want to know ...

Additionally, it does offer nice publishing to servers - with a comfortable wizard for setup and checking. But this stupid wizard provides no meaningful information during the check and already gets a timeout with a simple SFTP connection - and that is on a server where I am already logged in via SSH in a terminal window in parallel.

I saved myself the trouble of realizing publishing in any other way (e.g. in a local directory and then subsequent copying to the server) in view of the horrendous memory and CPU load. That's why there are also no statements about the generated HTML.

Sorry, I understand that Karelia wanted to get the beta out quickly - especially in view of the iWeb announcement. But then maybe you should write that the software is completely unusable on a Mac Mini. Not even Aperture is such a resource hog ...