Public User Feedback request - Promises

[benjamingr]

Following discussion in #76 and nodejs/promise-use-cases#26 we want to get some questions going for the Node.js promises usability and debuggability survey.

Going to try something - let me know if it's inappropriate :)

Post questions as comments - use 👍 and 👎 in order to indicate whether you think other questions should be included in the survey or not.

You are welcome to post question suggestions even if you are not Node.js project core. If you would like to consult me before posting a suggestion - feel free to contact me personally at benjamingr@gmail.com

[benjamingr]

What is your primary role in your workplace?

• Developer, I typically am not the person to debug production issues
• Developer, I typically am the person to debug production issues
• DevOps / Operations Engineer, I typically am not the person to debug production issues
• DevOps / Operations Engineer, I typically am the person to debug production issues
• Other (please specify)

[benjamingr]

Which do you use the most often in order to write async code:

• Promises without async/await.
• Promises with async/await.
• Node.js standard (err, data) callbacks.
• I don't use any of the above at all.

[benjamingr]

Do you use async iterators and for await( loops with streams?

[benjamingr]

Which of the following tools do you use in order to debug Node.js code at least once a week:

• The Node.js inspector or an IDE debugger (nodejs --inspect)
• Long Stack traces with an external library like Bluebird
• Printed stack traces with native promises (for example mocha errors).
• core dumps + lldb
• gdb
• Adding console.log around code and running it

[benjamingr]

What should the policy Node.js takes when an unhandled rejection occurs? For example - when an exception is thrown in an async function (or a then handler) but no code handles the error (.catch, then second param or catch in an async function).

• I would expect Node.js to abort the process like on uncaught exceptions.
• I would expect Node.js to stay silent about the error.
• I would expect Node.js to warn about the error. Note: this is the current behavior.
• I would expect something else.

Note: this is only the default and users would still have the ability of code to opt into different behaviour.

[benjamingr]

Do you use promises with async_hooks?

• I do not know what async_hooks are.
• I do know what async_hooks are but am not using them at all or with promises.
• I am using a third-party library that uses async_hooks with promises
• I don't know if I am using promises with async_hooks
• I am using promises with async_hooks in my code

If you answered "I am using promises with async_hooks in my code" to the previous question - please elaborate how?

_Enter answer here_

[benjamingr]

Is the performance of Node.js promises sufficient to you:

• Node.js promises are still slow (even on the latest version) and significant effort needs to be put in before I can use them.
• Node.js promises are slow - and while I am using them I think more time should be spent on optimizing them .
• Node.js promises are fast and more effort should be spent on making them more debuggable rather than faster.
• Node.js promises are fast enough now and I wouldn't mind them being slightly slower if that provides better debuggability features such as async stack traces in production apps.
• Node.js promises are not a limiting factor in my app's performance and I wouldn't mind them being slightly slower if that provides better debuggability features such as async stack traces in production apps.
• None of the above apply.

If you have answered that Node.js promises are slow, please write down why that factor limits your usage of promises:

__Enter answer here__

Note: see this note

[boneskull]

@benjamingr

What is your primary role in your workplace?

What's the necessity of this?

A large proportion of Node.js users are using it for tooling; Node.js may only be used to bundle a site or run tests. Those users may say they aren't using Node.js in production (I would).

Which do you use the most often in order to write async code:

Is this "which do you use most often" or "which do you prefer?"

Do you use async iterators and for await( loops with streams?

Maybe this question could use a code example. 😉

Which of the following tools do you use in order to debug Node.js code at least once a week:

Maybe "IDE or Editor" should be added to this list. I debug from VSCode wherever possible.

Is the performance of Node.js promises sufficient to you:

Users may not have an opinion, not care, or don't know.

But otherwise, unless the user is running Node.js 10, will the feedback be useful? If they complain it's slow, and they're using Node.js < 10, would it be an impetus to backport Promise performance improvements?

(Apologize if some of these have been answered already; I was not in attendance at relevant meeting)

[benjamingr]

@boneskull

What's the necessity of this?

A large proportion of Node.js users are using it for tooling; Node.js may only be used to bundle a site or run tests. Those users may say they aren't using Node.js in production (I would).

To validate that our survey reached a diverse set of developers - and to check the bias of various groups. For example in the meeting some participants mentioned they believe operations engineers use post-mortem debugging techniques differently from developers.

Is this "which do you use most often" or "which do you prefer?"

It is "which do you use most often".

Maybe this question could use a code example. 😉

Not really sure, it's basically "whether or not you have for await in your code or not.

Maybe "IDE or Editor" should be added to this list. I debug from VSCode wherever possible.

👍 added thanks

But otherwise, unless the user is running Node.js 10, will the feedback be useful? If they complain it's slow, and they're using Node.js < 10, would it be an impetus to backport Promise performance improvements?

Well - if people complain they're slow then sure - but there is a possibility they won't. If people complain about performance in older versions that's something to keep in mind as well.

More question suggestions welcome by the way.

[giltayar]

Which of the following tools do you use in order to debug Node.js code at least once a week:

I believe you forgot:

• Regular stack traces with native promises

Which is what I use to debug my tests when I'm not running them under a debugger (looking at the stack trace helps me figure out what the problem is.)

[benjamingr]

@giltayar Regular stack traces with native promises can you show me an example of what you mean exactly? Just looking at hte output of unhandled rejections?