take a peek at http://howtonode.org/ - some stuff is out of date as node is a rapidly evolving platform, but most of it holds true.

What do you mean? This was a conversation I had with him.

non-enterprise is scary to the enterprise

exactly what i thought. the chap actually wants Node to mature & become Tomcat! Maybe when he reads about NowJS he'll want them to mature & become RMI. Heh

Somewhat unrelated, but anyone interested in NowJS should definitely check out https://github.com/substack/dnode first...

How do you rationalize including logic in the markup?

Presentation logic requires logic. If a designer decides to display a bunch of items as three columns rather than two columns, or to switch the display for a single item vs a number of different items, that's presentation logic. Ideally it should go in the template, if that's where you've chosen to keep it.

With Django, I often find myself writing view logic to support specific presentation tasks (regrouping items in a manner more complicated than Django's {% regroup %} template tag allows, for example). This used to bother me, but then I decided that pragmatism beats purity if you actually want to ship anything.

just to be clear, jsdom is not a parser. By default it uses node-htmlparser which is not very lenient.

Have you tried using Aria's html5 parser? I hear it works better with malformed markup.