> Promises, Async, Generators, Redux Saga all solve these issues.
I'm aware of all of these and group them in with "callback hell." "Solve" is being overly generous. Generators are the best but still feel shoe-horned in and clunky.
> you either love it or hate - its not a hindrance. I love using ES7 over coffeescript now.
Yet another example of a language that you can't actually write a Node.js application in without transpiling...
> Putting the correct version numbers in your package.json and having your own NPM repo like Nexus (live Java) get rid of these issues.
So basically "don't use the system as intended" lol
> What?
Scaling is a pain in the ass.
> If any good programmer does not choose the right tools for a job then your not good.
This is an oft parroted phrase (usually by over-zealous project managers) to justify using some trendy new technology as though people hadn't been able to write HTTP servers until last year. There is more in common with all of those options I listed than there is difference. Twitter was serving millions of users before migrating away from Ruby on Rails. Instagram and Pinterest are in the top 50 most visited sites in the world and still both use Python+Django. If any programmer can only get the job done with a single tool, then they probably aren't that good.
I'm aware of all of these and group them in with "callback hell." "Solve" is being overly generous. Generators are the best but still feel shoe-horned in and clunky.
> you either love it or hate - its not a hindrance. I love using ES7 over coffeescript now.
Yet another example of a language that you can't actually write a Node.js application in without transpiling...
> Putting the correct version numbers in your package.json and having your own NPM repo like Nexus (live Java) get rid of these issues.
So basically "don't use the system as intended" lol
> What?
Scaling is a pain in the ass.
> If any good programmer does not choose the right tools for a job then your not good.
This is an oft parroted phrase (usually by over-zealous project managers) to justify using some trendy new technology as though people hadn't been able to write HTTP servers until last year. There is more in common with all of those options I listed than there is difference. Twitter was serving millions of users before migrating away from Ruby on Rails. Instagram and Pinterest are in the top 50 most visited sites in the world and still both use Python+Django. If any programmer can only get the job done with a single tool, then they probably aren't that good.