Genuinely intrigued and interested, how is this different/better?
Edit: Oh yeah I forgot HN isn't about answering honest questions, if you dislike something then you downvote it... fucking lame.
The site doesn't do much to explain that though, so here's a presentation:
https://speakerdeck.com/zcbenz/node-webkit-app-runtime-based...
Edit: Oh yeah, sometimes folks do answer honest questions ;)
Nothing to do with a server framework as it's at the other end of the pipe. ;)
That somebody didn't know about deployment (server vs. client) differences between two young frameworks for building single page applications?
My first reaction was that the projects are completely different and the question must have been grounded in a complete misunderstanding of what NW is, but as I think more I realize that there are some notable similarities.
Meteor synchronizes the clients and server in such a way that it seems they're running in the same process on the same machine, and the only thing the developer need worry about is adding some declarative configuration for security and efficiency (obviously this simplifies things a bit).
NW actually makes the client and server run in the same process on the same machine (or rather the parts of the stack that typically run on the client and server respectively).
The parent comment asked a question which may well have provoked an interesting discussion into a topic like this. And although its phrasing may have been a little blunt, it didn't come across as rude. If we assume that evo_9's comment was honest confusion rather than laziness, it's then only fair to assume Kiro's was founded in genuine interest as to where the confusion lies.
Now that I think about it they are both quite similar ("build apps with node.js/html/js/npm") and very different at the same time (webserver vs chromium runtime), so both questions are fair.