I find it funny that I was down-voted so for this. I haven't maligned the project at all; in fact, I think it's incredibly cool, I'm just not a huge fan of node.
I downvoted you because negative nonconstructive comments may as well not be posted. They provide no tangible benefit to anyone who participates in the discussion.
If you have a compelling reason as to why this project would be better done in another language then it would be prudent to include this reason in your original post. If all you're going off is personal preference then it may be best to keep this to yourself.
I understand your hope for comments to be constructive, and if you would like to have a discussion about the negatives of Node, it seems like that might be better on an article actually discussing that (though I will include them in this post to sate your curiosity :P). Additionally, I did not wish to start a flamewar (which always happens when you get into a discussion about the relative merits of a language on the internet).
My reservations about Node stem from this kind of app actually; the creation of a tool that goes far beyond the realistic and sensible use-case for Node.
That is, the huge benefit that Node offers is the ability to have both server- and client-side scripting in the same language; that's awesome. However, it's a fairly common bit of knowledge that JS is less than ideal for a wide variety of reasons (e.g., no integers, breaking the commutative property, etc.). While it may be a great alternative to PHP, it's still not that great of a language. So, to go beyond the notion of just using it to unify the language for webapps and to start creating userland applications on such a platform seems very counterproductive to me.
In this case, I am especially taken by the fact that this author has made three or four projects which all do similar things but for different use-cases. If this project were made into, for example, a C library, all of the derivative projects could just source that library and be simpler for it. Not to mention the fact that other projects could interface with it as well.
Despite C's reputation as being rather hard to make portable code, a public API with a C library actually makes it incredibly portable and extensible.
Again, I am completely okay with Node (I don't crusade against its existence), it just saddens me to see such cool projects be based on such a platform when there are obvious benefits to using something closer to the metal.