Can we simplify the callbacks pseudocode please? about art-of-node HOT 7 CLOSED

ps. I can submit a PR, just let me know which of the above things you'd prefer. Upon reflection probably the very last suggestion right?

from art-of-node.

@samjewell I'm not sure your example will work, as the thenRunThisFunction will be invoked before the asynchronous waitAMinute callback is called.

If you are still stuck on this (which I doubt as it's been over a year 😵), please open a PR. Thanks!

from art-of-node.

what would you say to renaming waitAMinute to waitAMinuteAsync? For extra clarity...

from art-of-node.

The fact that one of waitAMinute's arguments is a function is a clear indication that it's an asynchronous function. But if you think changing the name makes it more clear, please send a PR and I'll have a look.

from art-of-node.

I think that for us, developers - this is clear that this function will be an async one. But if we want to clarify everything related with javascript callback functions, their (people who are learning from this repo) brains are already melting with that amount of information. We need to treat them (without insulting!) like kids who are learning alphabet. Everything just must be big and bold ;)

from art-of-node.

The fact that one of waitAMinute's arguments is a function is a clear indication that it's an asynchronous function

Is it? Couldn't I have a function that takes another function as an argument, but operates synchronously? I'm sure some lodash functions do that. Eve if they don't I could write one, surely?

Agreed to someone who has some experience with JS this 'looks like' an async function, but the only way to find out for sure is to try it out / look at the sourcecode / docs, isn't it? Or am I wrong somewhere?

from art-of-node.

Function renamed here: #65

from art-of-node.