Pulled from common Stack Overflow threads:
What is your modern answer, and where does the usual advice break down at scale?
Ellen
Return a Promise and make the async boundary explicit.
WaffleFries
You do not return the eventual value synchronously, you return a Promise or await it, but the production caveat is making cancellation, timeout, and error shape explicit so callers are not guessing.
Ellen
The advice breaks down when people treat async as the whole design, because in production the real API is the contract around aborts, retries, and whether failures are values or thrown errors.
Arthur
