3 ms·

I applied for a backend and told them I did node.js and does javascript dev (which they were looking for). They tested me on front end shit. And thinks that ja

I applied for a backend and told them I did node.js and does javascript dev (which they were looking for). They tested me on front end shit. And thinks that javascript is only front end. While there are many down falls with node.js it still pay the bill, interest tech, and I wish people would realized that just cause you program js you doesn't imply that you want to do front end. I hate front end. It's just not for me.

collyw 13y ago
Unless you are handling massive amounts of concurrent connections, are there not better choices than Node for the server side? Its still a fairly new technology.
- tracker1 13y ago
  Node does offer a lot of advantages beyond just many concurrent connections... A single language paradigm for client and server is big... the exact same language/structure/models for client and server communications and validation is pretty big. Many client-side tools utilize node.js these days as well. In general node.js combined with npm bring a lot less friction to development than other languages. Using node to create shim services for a front end communicating through to different backands is brain dead simple as well. In fact there's been a few times that creating a service in node.js to communicate with an ill-defined backend was so much easier in node compared to the static language the main application was working in it was a no brainer. Utility scripts in JS can also be pretty useful.. any kind of stream manipulations work well in node.js too. This doesn't even mention that JSON (current data transmission structure du jour) is native to the environment. And storage systems like MongoDB (couch, rethinkdb and others) is really transparent to node. I couldn't even begin to all list the advantages, but here are a few.. the event loop system, libuv library bindings internal to node.js, language singularity, the npm system and over 40k modules...
  - jhh 13y ago
    The way I imagine node development is pure hell. You have this event loop where if you screw anything up your whole app immediately comes to a grinding halt. You don't have any mature standard library. Instead you have 8 gazillion libraries in different versions... Just overboarding complexety, unfindable bugs, dependency hell. And then you do all of it in JavaScript.
    - sethkojo 13y ago
      Node's event loop is very easy to work with since all the standard tools are async from the start. It's not like eventmachine where standard Ruby calls are synchronous and they can throw a wrench in your logic. There's no need for a mature standard library. Things move faster nowadays and you can't wait for things to get standardized. Node embraces the open-source spirit and trusts that the best libraries will rise to the top eventually. And then you do all of it in JavaScript. JavaScript is actually a top notch language. Cream of the crop. Lambdas, higher-order functions, apply/call, and OO. What more could you ask for from a dynamic language?
      - taybin 13y ago
        Integers.

collyw 13y ago

Unless you are handling massive amounts of concurrent connections, are there not better choices than Node for the server side? Its still a fairly new technology.

tracker1 13y ago
Node does offer a lot of advantages beyond just many concurrent connections... A single language paradigm for client and server is big... the exact same language/structure/models for client and server communications and validation is pretty big. Many client-side tools utilize node.js these days as well. In general node.js combined with npm bring a lot less friction to development than other languages. Using node to create shim services for a front end communicating through to different backands is brain dead simple as well. In fact there's been a few times that creating a service in node.js to communicate with an ill-defined backend was so much easier in node compared to the static language the main application was working in it was a no brainer. Utility scripts in JS can also be pretty useful.. any kind of stream manipulations work well in node.js too. This doesn't even mention that JSON (current data transmission structure du jour) is native to the environment. And storage systems like MongoDB (couch, rethinkdb and others) is really transparent to node. I couldn't even begin to all list the advantages, but here are a few.. the event loop system, libuv library bindings internal to node.js, language singularity, the npm system and over 40k modules...
- jhh 13y ago
  The way I imagine node development is pure hell. You have this event loop where if you screw anything up your whole app immediately comes to a grinding halt. You don't have any mature standard library. Instead you have 8 gazillion libraries in different versions... Just overboarding complexety, unfindable bugs, dependency hell. And then you do all of it in JavaScript.
  - sethkojo 13y ago
    Node's event loop is very easy to work with since all the standard tools are async from the start. It's not like eventmachine where standard Ruby calls are synchronous and they can throw a wrench in your logic. There's no need for a mature standard library. Things move faster nowadays and you can't wait for things to get standardized. Node embraces the open-source spirit and trusts that the best libraries will rise to the top eventually. And then you do all of it in JavaScript. JavaScript is actually a top notch language. Cream of the crop. Lambdas, higher-order functions, apply/call, and OO. What more could you ask for from a dynamic language?
    - taybin 13y ago
      Integers.