<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2008/05/13/joy</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/05/13/joy"/><id>http://norman.walsh.name/2008/05/13/joy/comments.atom</id><updated>2012-05-23T13:06:05.031634Z</updated><entry><title>Comment 1 on /2008/05/13/joy</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/05/13/joy#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2008-05-15T03:03:08Z</published><updated>2008-05-15T03:03:08Z</updated><author><name>Andrew Savikas</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>I had a very similar experience -- I felt a need to get my hands dirty with MarkLogic, and so found a defined, simple XML problem to solve (in my case, a dashboard view of content in Safari Books Online using the API).
</p>
    <p>
Less than 50 lines later, I had a pretty robust web app that's still running almost unchanged more than a year later. I was also definitely really that impressed. I'm still not quite sure why XQuery hasn't caught on more for web apps (especially those that consume XML and display as HTML).</p>
  </div></content></entry></feed>

