5 ms·
Not since I like using relational databases - MongoDB is the datastore of choice in nodeland and everything else is a secondary concern. Node's asyncronicity me
by bjourne 14y ago
Not since I like using relational databases - MongoDB is the datastore of choice in nodeland and everything else is a secondary concern. Node's asyncronicity means very little to me since it is trivial to run a pool of fcgi server processes behind nginx and get parallelism that way. It's also hard to avoid "callback hell" consisting of anonymous functions nested X levels deep in what in another scripting language would have been nothing more than a few statements after each other. I heard "promises" could solve that but then I gave up because I don't want to use something that complicated just to implement basic control flow.
I think Node definitely is the right tool for a lot of use cases, but for 99% of all web sites, it's not the right choice.
- codewright 14y agoI use MongoDB, but decided to stick with Python for similar reasons. The callback hell is an atrocity and Clojure pretty neatly demonstrates why it's 100% unnecessary.
- mike-cardwell 14y agoI've never had any difficulties using Node with MySQL.
- bjourne 14y agoIt's ok if you like running raw queries. But there's no decent orm you can use to abstract away the sql. node-orm does exist, but is currently very much alpha quality and does not offer nearly as many features as other orms in other languages.
- mike-cardwell 14y agoWell, I'm not too worried about that. ORMs just lead to slower code that is harder to maintain.
- rubentan 14y ago"Callback hell"? Just curious, have you looked into flow control libraries like async yet?
- bjourne 14y agoNope. I know about their existence but reasoned that if you need third party libraries for something as simple as sane control, flow then Node probably isn't ready. :) I'm planning to investigate them when I get time because they seem very interesting from a technical standpoint.