|
...for doing this article. I'm also very excited about XQuery in this capacity. The potential for simplification is massive!
No middle tier, no objects, no sql, no orm. No mismatch between the data in the database, the markup on the page, and the objects required to convert between the two.
Rather, XML documents in the database converted to XHTML documents for serving via a highly customized tool called XQuery. It's data all the way down, with no clumsy, heavy stages in between.
XQuery on the server won't be for everyone... lots of people will be too used to existing practice to try it out, even on new development...
I think the commenter who complains about 'starting over from scratch' is really missing the point... this isn't about starting from scratch, it's about a whole new paradigm with lots of advantages over the old. You're truly starting out ahead.
What's missing now is the 'Rails' or 'Struts' or 'Django' of the XQuery world... a web framework that reduces drudgery and duplication of effort with reusable XQuery functions and modules. Once that is available, XQuery on the server should see significant adoption, as the benefits of a data-centric approach will be extremely attractive compared to object-centric approaches of old.
|