Theres one severe problem in Safari for iPad, though: memory crapping out. MobileSafari for iPhone has always allowed you to open up to eight pages at a time. It tries to keep them all truly open, in RAM, so that you can quickly switch between them. But when it runs out of memory it starts flushing some of the pages. It doesnt forget the URLs for those pages, and, in recent versions, it saves a static thumbnail image of the rendered page, but when you switch back to those purged pages, MobileSafari must reload the page thus, you must wait both for the contents of the page to download and for the page to actually render (which the rendering often takes longer than the downloading). Its very noticeable. Switching between unpurged Safari pages is instantaneous. Switching to a purged page takes as long as opening it from scratch.
This purging problem got a lot better with the iPhone 3GS. The original iPhone and iPhone 3G only had 128 MB of RAM. The 3GS has 256. MobileSafaris ability to keep more pages in memory is probably my single favorite aspect of the 3GS.
The iPad also has 256 MB of RAM. But, in my use, iPads Safari isnt able to keep nearly as many pages open as I can on my 3GS. In fact, sometimes it seems I can only have one, and every page I switch to gets completely reloaded. This is more than just annoying it can lead to data loss if you have unsubmitted form data sitting in an open iPad Safari page. Ive run into this posting items to DF from the iPad my posting interface is a web page form. When I want to link to the current page, I invoke a bookmarklet which opens a new page with the title and URL fields of the posting form set to the title and URL of the page from which I invoked the bookmarklet. Often, though, I want to switch back to the page Im linking to copy another URL or a bit of text to quote. Twice so far, when going back to the posting form, its been purged and must reload from scratch in which case I lose anything Ive already written. I never run into this problem on my iPhone 3GS when switching between just two open Safari pages.
The problem is also severe for AJAX web apps, which tend not to be designed with full page refreshes in mind.
I hope this can be improved significantly in an iPad software update, but I worry that its endemic that because the iPad screen is so much larger than the iPhones, that MobileSafari must allocate significantly more memory per page for the framebuffers. 256 MB of RAM simply may not be enough for MobileSafari to keep more than two or three pages in memory. If so, Apple really needs to consider some sort of caching or serialization scheme rather than completely flushing away purged pages.