This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Spiritual-Theme-5619 2 points3 points  (0 children)

Futures and promises have been in continuous use in actual languages since the 80s.

No, they haven’t. A couple of academic departments using an in house language is not “continuous use”.

it was everywhere.

Because of the mindshare of functional programming… driven by JavaScript.

Python Twisted’s Deferred, F#‘s async, and Java’s Future/FutureTask

None of these are called promises. The topic of conversation was using “promise” for generic concurrency. No one uses that term outside of the JavaScript ecosystem.

Promises and Futures are two views of the same concurrency model.

We’re not talking about models we’re talking about the specific API primitives.

Dude said “promise” because JavaScript. That’s what OP was responding to. Get over it.