4 ms·

Directory structures, module systems, package managers, build tools, communities, learning resources, etc. Also, the DOMs API and Node's could not be any more d

Directory structures, module systems, package managers, build tools, communities, learning resources, etc. Also, the DOMs API and Node's could not be any more different. Their concerns have literally nothing to do with one another. Plus, you really can't pick up a framework in a few weeks. There's a reason why people pay more for someone working in Rails for 5 years, than someone whose been using it for 2.

davedx 13y ago
I don't get how any of those are the "Node way", any more than they are the "Rails way" or the "Python way", or even the "PHP way" these days. I can only really think of two patterns I see in node.js that I don't see everywhere else: eventemitter and chaining middleware together with next() calls. Hardly something it takes 5 years to learn. ;)
- ulisesrmzroche 13y ago
  It doesn't matter where you see them, that's like saying that french and english are the same because they share some words. It's patterns that are particular to a certain community of developers, but of course, can come up in other languages. This is an example of a node-ism, if (err) { return err } console.log("KEEP GOING") Notice how we break from an error right away. As a Node developer, you may not use the pattern, but you're definitely aware of it. Someone with just JS, and let's be honest, jQuery, is not used to returning quickly if there is an error. Decorating and animating a UI is far more forgiving. I's not about how long it takes to learn a certain module. It's about mitigating risk in building large web apps.
- Touche 13y ago
  > I don't get how any of those are the "Node way", any more than they are the "Rails way" or the "Python way", or even the "PHP way" these days. Well, they're specific to Node and therefore have to be learned, to some extent. There's also a million other things, some little some big. Little -> knowing that the first argument of a callback is an error. Big -> Understanding Streams. Medium -> the use of small modules, knowing when to break up a file into smaller modules, knowing when to break up a project into many modules, etc.
  - ulisesrmzroche 13y ago
    'directory/index.js' is another of those. Also, module.exports. Bigger would be like knowing that express has one hoof at the glue factory because koa is bringing mad generators. Also, there's just some stuff you know when you're working with Node all day. Same thing with every profession and specialities. If you work in Rails all day, your'e going to know a hell of a lot more about it than me. I can't just pick up what you know in a weekend.

davedx 13y ago

I don't get how any of those are the "Node way", any more than they are the "Rails way" or the "Python way", or even the "PHP way" these days. I can only really think of two patterns I see in node.js that I don't see everywhere else: eventemitter and chaining middleware together with next() calls. Hardly something it takes 5 years to learn. ;)

ulisesrmzroche 13y ago
It doesn't matter where you see them, that's like saying that french and english are the same because they share some words. It's patterns that are particular to a certain community of developers, but of course, can come up in other languages. This is an example of a node-ism, if (err) { return err } console.log("KEEP GOING") Notice how we break from an error right away. As a Node developer, you may not use the pattern, but you're definitely aware of it. Someone with just JS, and let's be honest, jQuery, is not used to returning quickly if there is an error. Decorating and animating a UI is far more forgiving. I's not about how long it takes to learn a certain module. It's about mitigating risk in building large web apps.
Touche 13y ago
> I don't get how any of those are the "Node way", any more than they are the "Rails way" or the "Python way", or even the "PHP way" these days. Well, they're specific to Node and therefore have to be learned, to some extent. There's also a million other things, some little some big. Little -> knowing that the first argument of a callback is an error. Big -> Understanding Streams. Medium -> the use of small modules, knowing when to break up a file into smaller modules, knowing when to break up a project into many modules, etc.
- ulisesrmzroche 13y ago
  'directory/index.js' is another of those. Also, module.exports. Bigger would be like knowing that express has one hoof at the glue factory because koa is bringing mad generators. Also, there's just some stuff you know when you're working with Node all day. Same thing with every profession and specialities. If you work in Rails all day, your'e going to know a hell of a lot more about it than me. I can't just pick up what you know in a weekend.