News for hackers. Stuff that matters.

A comment on When Node.js is the wrong tool for the job. Parent comment

Re:When Node.js is the wrong tool for the job by PCaponetti on Friday January 06, 2017 @08:38AM (#13336093)
async / await allows you to choose how async you want your code to be/look, and I for one like to have a choice as opposed to say other languages that don't always have an async option.
[ Parent | on HN ]
Re:When Node.js is the wrong tool for the job by ldev on Friday January 06, 2017 @09:59AM (#13336688)
C# has this same async await. The only difference - I can choose to use sync workflow by appending .Result to async function, ie `var response = asyncFunction().Result;` .....

Node.js is garbage (well, good for simple crud apps) and so is JS.

[ Parent | on HN ]
Re:When Node.js is the wrong tool for the job by Klathmon on Friday January 06, 2017 @10:19AM (#13336892)
But with async/await in JS, you just prepend an `await` and you get the sync workflow.

That being said, I do like how C# handles it more than the way JS has handled it, but both are fantastic.

You can say JS is "garbage" all you want, but it's close to the most popular language on the planet and many many people are writing great things because of it.

[ Parent | on HN ]