As you can see from the video above, the iPad 2 using the Apple A5 chip combined with more RAM performs much better than the original iPad when browsing in Mobile Safari. If you load up all nine tabs, you’ll see that the original iPad starts to choke up pretty badly when compared to the iPad 2. This is due to the original iPad only coming with 256MB of RAM while iPad 2 comes packed with 512MB. (We hoped for as much as 1GB in the video before getting more test results back. Maybe next year!.)

The original iPad tends to “kill” background tabs whenever it runs out of available memory, which can get pretty annoying if you use the iPad primarily for web browsing. The iPad 2 performed flawlessly and had no hiccups when browsing. Also the dreaded “checkerboard effect” — where significant lag would occur before Safari could render the web page content — is nowhere to be found. Scrolling in Safari is smooth as butter, and gone are the days when switching between tabs meant loading the entire page from scratch.

The difference in performance is quite clear, and browsing on the iPad 2 is definitely a step up from the original iPad in every way. If you were able to pick up an iPad 2 then let us know your thoughts on RAM performance and how it compares to the first iPad in the comments below!

Tap and hold is a multi-touch gesture that Apple introduced into Mobile Safari in iPhone OS 2.0. It triggered a popup a menu that allowed users to Save Image to the camera roll.

In iPhone OS 3.0 it’s been given a bit more power. Now, in addition to selecting blocks of text for Copy and Paste, when you tap and hold on a link, you trigger the same type of popup as the Save Image function, but instead you get the URL path for the link and options to Open (in the same page/tab), Open in New Page (tab), or Copy (the URL path).

If the link is also an image, you get all of the above options, with Save Image combined into the mix.

May not seem as sexy as MMS or Stereo Bluetooth but we heart this new functionality. It will make our lives easier, which is what OS updates should do.

We’ve mentioned this in passing before, but the parallels, if any, are worth making more prominent.

Using webOS, which is a localized, almost widget-ized development environment (using HTML, CSS, JavaScript, and enhanced local access), the Palm Pre can run many WebApps at the same time. The way it’s visualized is with the “card” metaphor, where a touch of the Home-like button shrinks the current screen down to a thumbnail that’s kept live and updated in real time. The interface also lets users shuffle the apps like cards in a fanned-out deck. You re-arrange the cards and can even terminate an app by “throwing it away”.

While the iPhone doesn’t keep them live or let you re-arrange them, and has an X to close rather than the throw-away gesture, going as far back as two years ago when Steve Jobs introduced it at Macworld 2007, it let you zoom out of the Mobile Safari web browser with an eerily similar thumbnail representation. (Though there doesn’t seem to be any patent contention over that just yet…)

Actually, given Apple’s recent obsession with Cover Flow in iTunes, OS X 10.5 Leopard’s Finder and now Safari 4 Beta, we’re surprised they didn’t just default to that for Mobile Safari tabs from the get go as well…