5 ms·

Id have to disagree with that myself. While node and mongodb are both "shiny" they are because they solve a problem that people have and offer solutions to pro

Id have to disagree with that myself. While node and mongodb are both "shiny" they are because they solve a problem that people have and offer solutions to problems that are very appealing. Including as i mentioned i blieve in another comment here that using node allows you to only have ot work with one language. Which is great. So its true that python has similiar technologies such as tornado and twisted. But if node works then why not just stick to one technology to have to maintain rather then multiple ones. Also node has a great community that is increasing. Many python libraries dont have this. Meaning really documentation. For example tornado has very little documentation.

dextorious 15y ago
"Id have to disagree with that myself. While node and mongodb are both "shiny" they are because they solve a problem that people have and offer solutions to problems that are very appealing. " A lot of people use them for solving problems they DON'T have. Lots of people use both Mongo and Node.js at ill-fated attempts at premature scaling (similar to premature optimization).
- clojurerocks 15y ago
  Again i will disagree with you on that. One of the benefits of node and why its becomingly increasingly popular is that it allows ease of development with the benefits of scale built in. So you dont have to worry about a steep learning curve for a simple application that only a few people will ever use. Or that youre framework is easy to develop with but what happens if it becomes popular. What then. This is even more the case with todays applicaitons which incrasingly are "api" based with the web framework portion being used just to serve the ajax code and for urls and whatnot. With node you get all of it together. Also if node used some other language that wasnt a standard this might also be true. But again it uses javascript or coffeescript which is becoming more and more used all f the time. Even in mobile applications and gaming now with canvas. Obviously if you know python or ruby or php extremely well and can build whatever you need quickly with that then theres no reason not to. I was new to python so it wasnt a major switch for me.
  - bretthoerner 15y ago
    > it allows ease of development with the benefits of scale built in How is scale "built in" to Node any more than any other modern language/runtime?
    - sneak 15y ago
      It's not - it's built out, actually. "I want to scale my app on modern, multi-core computers. I know, I'll write everything so that it all runs in a single thread!"
      - mnutt 15y ago
        I want to scale my app on modern, multi-core computers. I know, I'll write everything so that it all runs in a single thread! This is the same fallacy that gets repeated every time node is mentioned. If you're scaling up past a single machine you have to figure out how to share state between multiple machines anyway, so you may as well run a process per core. Then you have a single way to share state, rather than one way between cores and another between machines. So unless you're writing a desktop app that needs to scale up but only to all of the cores of a single machine, you're sometimes better off simplifying the state-sharing logic.
        sneak 15y ago
        You can get that all basically for free using something like ZeroMQ, without all the cancer, and with bindings for a Real Language.
        mnutt 15y ago
        Uh, that just proves my point that you don't need a multithreaded app to do so. And your 'cancer' language is unhelpful. What are you afraid of? That somebody somewhere is using a bad language when a better one is available? That the NodeConf organizers reserved all of the good hotel rooms? Why are you so angry at a programming community?

dextorious 15y ago

"Id have to disagree with that myself. While node and mongodb are both "shiny" they are because they solve a problem that people have and offer solutions to problems that are very appealing. " A lot of people use them for solving problems they DON'T have. Lots of people use both Mongo and Node.js at ill-fated attempts at premature scaling (similar to premature optimization).

clojurerocks 15y ago
Again i will disagree with you on that. One of the benefits of node and why its becomingly increasingly popular is that it allows ease of development with the benefits of scale built in. So you dont have to worry about a steep learning curve for a simple application that only a few people will ever use. Or that youre framework is easy to develop with but what happens if it becomes popular. What then. This is even more the case with todays applicaitons which incrasingly are "api" based with the web framework portion being used just to serve the ajax code and for urls and whatnot. With node you get all of it together. Also if node used some other language that wasnt a standard this might also be true. But again it uses javascript or coffeescript which is becoming more and more used all f the time. Even in mobile applications and gaming now with canvas. Obviously if you know python or ruby or php extremely well and can build whatever you need quickly with that then theres no reason not to. I was new to python so it wasnt a major switch for me.
- bretthoerner 15y ago
  > it allows ease of development with the benefits of scale built in How is scale "built in" to Node any more than any other modern language/runtime?
  - sneak 15y ago
    It's not - it's built out, actually. "I want to scale my app on modern, multi-core computers. I know, I'll write everything so that it all runs in a single thread!"
    - mnutt 15y ago
      I want to scale my app on modern, multi-core computers. I know, I'll write everything so that it all runs in a single thread! This is the same fallacy that gets repeated every time node is mentioned. If you're scaling up past a single machine you have to figure out how to share state between multiple machines anyway, so you may as well run a process per core. Then you have a single way to share state, rather than one way between cores and another between machines. So unless you're writing a desktop app that needs to scale up but only to all of the cores of a single machine, you're sometimes better off simplifying the state-sharing logic.
      - sneak 15y ago
        You can get that all basically for free using something like ZeroMQ, without all the cancer, and with bindings for a Real Language.
        mnutt 15y ago
        Uh, that just proves my point that you don't need a multithreaded app to do so. And your 'cancer' language is unhelpful. What are you afraid of? That somebody somewhere is using a bad language when a better one is available? That the NodeConf organizers reserved all of the good hotel rooms? Why are you so angry at a programming community?