Nonetheless, it seems that decades of training have taught people that "sites are made of documents and scripts, but apps are written with code and APIs". I'm feeling kind of bitten by this perspective with the release of SenchaTouch, an API-based app framework that does amazing things but discards the document-based approach of jQTouch, also created by David Kaneda Colby.
With respect to jQTouch vs. Sencha Touch, jQTouch is a good solution for people who need some progressive enhancement of web content, but it's not a full application framework.
That's really strange to me. The contrast I see is "progressive enhancement of web content" vs. "application framework", but somehow he qualifies the former with "some" and praises the latter with "full". My phrasing would be more like:
With respect to jQTouch vs. Sencha Touch, jQTouch is a good solution for people who need to turn content into a full-fledged app experience, while Sencha Touch is an application framework meant for people whose focus is primarily code-based interactions.
What's the difference?
I encourage folks who want to be programmers to give Sencha Touch a close look. For my own content-centric work, though, the jQTouch approach seems vastly more appropriate. Hopefully it'll see a vigorous revival.