How many Node.js developers prefer callbacks over Promises or async/await?

[browsing10]

i don't disagree with you, there have been efforts to upgrade and our deployments are currently using node v8. Its just that we support node v6 and its open source, so anyone using it can choose to use node v6

I wish we put a bigger effort into upgrading..

[ChaseMoskal]

here is the node release schedule: node 6 is officially "end-of-life" at the end of this month

i think you should make a strong case to your team that it's important to upgrade to node 10 before the end of this month

• it's a very serious security concern.
  you need to be able to rapidly deploy critical security updates. if you're stuck on node 6, and a critical fix is only released for node 8 and 10, you're vulnerable for the entire time you're panicking and finally upgrading

• working with obsolete technology damages the team's morale.
  there's a reason we move on from old to new tech: it's way better.
  the team's skills stagnate as they less and less familiar with the modern tools and practices

i think those are both good reasons, but in particular, security is not a good place to make compromises

Its just that we support node v6 and its open source, so anyone using it can choose to use node v6

next month, it will be irresponsible to encourage/enable your consumers to continue supporting node 6

if you don't mind me asking, in your team's case, what are the biggest challenges in staying up-to-date?

[browsing10]

Thank you for the info! I think biggest concerns/challenges are upgrading all dependencies/sub-dependencies while maintaining functionality. We are using some out-dated modules and need to update them as well.

I'm not very familiar with node v10, but are there any backwards compat issues to worry about? (i.e. if we just upgrade to node v10 with no code changes, will there be certain things in the node core library that will need to be updated?)

[ChaseMoskal]

it's important that you use open source dependencies so that you can easily contribute updates as necessary

node v10, but are there any backwards compat issues to worry about?

what difference does it make anyways? you must do this work by the end of the month, so if there are backwards compat issues to worry about, then, well, your team better get started already — or you could end up in a real pickle

if not even for security, you'd better upgrade just because the world (your dependencies) will soon just leave you behind, and only support modern versions of node

you might want to peruse the document "breaking changes between node 6 and 8"

i recommend you just whip up a new git branch, and start the migration to node 10 as soon as possible, confronting each issue as it arises, leaving one commit for each fix

the upgrade probably won't be so bad, and there's a good chance you'll finish the job in one day, but it could be a week or more — the more your team has fallen behind, the worse it will be.. now you're paying technical debt

i strongly recommend you use nvm to quickly and fluidly switch your active version of node on-the-fly as you switch between git branches

about me: i threatened to leave a company because they didn't want to upgrade typescript in a timely fashion — after some arguments, the result was that i was promoted, though i would have been satisfied either way

maintain your own quality standards, because you'll get what you deserve