Cappuccino is in many ways more revolutionary and the SC, as it completely throws out any notion of dealing with HTML and CSS. By completely abstracting the presentation some things become easier, but some things become impossible (for example: they cappuccino devs haven't implemented all of CGGraphics, and that makes some things that are trivial in CSS, like rounding the corners of an image, effectively impossible). With SC you're working with HTML and CSS, though most of the HTML is generated by JS. I found the latter approach more flexible, especially if you can target CSS3-supporting browsers.
Both are based on cocoa, though Cappuccino takes its influences much more seriously. I love cocoa but I'm not terribly enamored with Obj-C syntax, so I don't really see why someone would want to take JS's superior syntax and replace it with Obj-C's, as cappuccino has done. Cappuccino also lacks a data store framework, while SC has a very good one.
Finally, SC uses native browser rendering as much as possible, which should make SC apps faster.
That said, I think Cappuccino has a lot of potential, and 280Atlas, a visual editor for cappuccino apps written in itself shows that. As it matures and the basically non-existent docs improve I think it will become increasingly worthwhile.