Seems like your prayers were answered. John Siracusa in an ArsTechnica review: "The most important changes to Safari in Mavericks are internal. Two years ago, Lion included a version of Safari based on the WebKit2 engine, which separated the task of page rendering and JavaScript execution into an external process, mostly for security reasons.
WebKit2 was a reaction to Chrome's multi-process architecture, which uses multiple WebKit processes to handle page rendering. Google included the multi-process code in the Chromium project, not in WebKit. Before creating WebKit2, Apple asked Google if it was willing to contribute Chromium's multi-process code to the WebKit project. Google declined, leaving Apple to create its own solution. Apple implemented its multi-process system in the WebKit engine itself, benefiting any application that uses WebKit.
Unfortunately, the WebKit2 era of Safari has been marred by chronic instability. When Safari's lone back-end Web rendering process gets wedged, users are greeted with the all-too-familiar "webpages are not responding" dialog; forward progress requires reloading every open webpage in every tab in Safari. This problem has not gone away in the years since Lion was released.
Contrast this to Google's Chrome browser, which has been rock-solid over the same period. The cumulative effect of these years of Safari instability has made me start to question whether Apple still has the chops to keep up in the fast-paced world of Web rendering engines.
Safari version 7, included in Mavericks, is Apple's answer. It sports a new process-per-tab architecture, finally following in Chrome's footsteps—though this change is part of WebKit itself, not just the Safari application. It's too early to tell if this change will restore Safari's stability, but I can report that I have not seen a single Safari crash or "webpages are not responding" dialog in all my Mavericks testing. (I've seen many in Safari 6 while writing this review in Mountain Lion.)"
This may also be a reply to those who say to Apple, "just fix it"; Apple's been obviously thinking about this for years. It's kinda like you want your '64 Ford to run like your Prius - it ain't gonna happen in one day.
Read the rest of the Safari review, and then read the rest of his review: http://arstechnica.com/apple/2013/10/os-x-10-9/4/