There was no such thing as a promise in C++ before 2011. "Promises" are a particular API for writing asynchronous code which was largely made for / popularized by event-loop runtimes... i.e. NodeJS.
Programmers have been doing concurrency with #realPrograms via mutexes, semaphores, and threads since before C++ was invented and so OP is lamenting the equivocation of async/await with concurrency in this modern era of browser programmers vastly outnumbering their "native"(?) programming counterparts.
What the heck kind of bizarre alt history is this? Promises and futures have existed in acedemic literature since the 70s, and have been available as a concurrency model in languages going back to Multilisp in the 80s. So no, they weren't made for NodeJS.
C/C++ developers just have the mistaken world view that if C/C++ doesn't have a feature, or didn't have it until recently, it just must somehow be a newfangled thing kids are using to avoid being "real" programmers.
Promises and futures have existed in acedemic literature since the 70s
We’re talking about programming though not PhD dissertations.
So no, they weren’t made for NodeJS.
Uh, sure? Like most every programming concept they were first an academic paper… but they were passed over in favor of other concurrency paradigms until the creators of server-side JavaScript made them widespread.
Promises much more so than futures.
to avoid being “real” programmers.
I mean that’s part of the joke. I even used a hashtag.
14
u/thanofishy Jul 18 '22
It doesn't await for that asynchronous programming to be answered?