doc: fix recommendation of setImmediate() over process.nextTick()

[davalapar]

Is your feature request related to a problem? Please describe.

On this url:

• https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/

At the process.nextTick() section, it says:

We recommend developers use setImmediate() in all cases because it's easier to reason about (and it leads to code that's compatible with a wider variety of environments, like browser JS.)

But this is untrue since setImmediate() isn't supported in "wider variety of environments". Only supported in Edge & IE, but not Chrome, Firefox, Safari (on both desktop and mobile platforms).

• https://developer.mozilla.org/en-US/docs/Web/API/Window/setImmediate
• https://caniuse.com/#feat=setimmediate

Describe the solution you'd like

• remove that last phrase "(and it leads to code that's compatible with a wider variety of environments, like browser JS.)"?

Describe alternatives you've considered

• I think setTimeout and window.requestAnimationFrame are the nearest alternatives for setImmediate for the browser, but I don't know how to phrase it yet

[Fishrock123]

That phrase should probably be removed.

If we wanted compatibility notes, setTimeout(1, ...) works in most cases in the browser where you'd want a setImmediate, and Promise.resolve().then(...) works as a counterpart to process.nextTick(...) (and also works in node, but you should avoid ever doing that in node).

[devsnek]

queueMicrotask too.

[szhigunov]

I would like to start with that.

[navin1551]

Hi, is this still open to work on?

[szhigunov]

Hi, is this still open to work on?

Hi, I'm working on that issue now.

[szhigunov]

@Fishrock123 I created a PR where I removed that phrase. Could I somehow improve that section?