Except Node.js isn't a framework for building websites/web applications.
Also from the article: You'll not have headaches regarding concurrency (at first), but you'll have them when dealing with callbacks. For some cases I almost ended up with one callback per line, that's crazy!
People that write stuff like that are very ignorant and are probably trying to write Javascript like they write their Java.
I mostly try a framework to see what it can do. Looking at the documentation it seems like they are good enough to get me started.
Not sure what all these negative comments are doing here. Feels like half the people are asking for somebody to hold their penis and the other half is crying because they can't read Coffee-Script.
I also use knockout.js for a project and batman.js looks like it has some similarities but it seems to be filling some holes that knockout.js leaves you to fill your self.
Which, I think, is not a huge deal with Knockout, just a difference. In our case we're using it for widgets included on other people's sites, so it's not a conventional web "application" with "pages" (I don't think we'd use the routing bits of batman.js at all, for instance).
Also from the article: You'll not have headaches regarding concurrency (at first), but you'll have them when dealing with callbacks. For some cases I almost ended up with one callback per line, that's crazy!
People that write stuff like that are very ignorant and are probably trying to write Javascript like they write their Java.