The last nail is certainly not in the coffin but I am almost an OmniWeb Convert.
Why would a lifer in the Mozilla fold now take to the sexy curves of the native webkit browser world?   It all comes to bloat and instability in Firefox 3.5.  After a suggestion from my friend Grant, I gave the OmniWeb browser a fair shake.   I am going to run down the highlights and low lights in this post from a perspective of someone who just wants shit to work.

Pro’s:  (For OmniWeb)
- Native Webkit kicks ass.   You can’t quite keep track of these performance numbers between Firefox / Safari / Opera / the rest (Chromium?), but this feels fast.
- 4 hours of browsing later:  it still feels fast.   Firefox was a life of restarts to keep the performance consistent.
- Tab Management:  I am growing to like the tabs on the left side with thumbnails of what I am browsing.   This was not immediate.
- Developer friendliness:  Being able to leverage the Inspect capability of OmniWeb makes me a better web citizen.
- Form size management:  I can resize any input field in the browser:  Slick.

Con’s:
- Firefox Plugin’s:   Duh.
- No Automated way to manage AdBlocking lists.
- Native Spell check lets you know you misspelled something but no suggestions?!!  WHY?!
- No easy way to import my bookmarks from Firefox:  (No easy way to export them either)
- The Googles / Facebook wreak havoc:  Sites that are perpetually updating with new data tend to never render the title bars correctly.  Take Gmail as an example where I can’t get a decent read on when I have a new mail message.  I think this bug was fixed in the latest webkit however.

If someone has any tips or tricks to make the OmniWeb experience a bit more friendly please pass them my way.  I am going to keep updating this post as I continue to become more acclimated.