Re:Why is learning functional programming so damned hard? (2...
by Jasper_ on Sunday August 15, 2021 @11:12AM
(#28189402)
As far as I know, the Future concept for async/await started with Twisted's Deferred, which is a framework for Python. It's not really from functional land.
[ Parent
| on HN ]
Re:Why is learning functional programming so damned hard? (2...
by nextaccountic on Sunday August 15, 2021 @11:34AM
(#28189582)
Futures were first proposed in 1976, in a book called "The Impact of Applicative Programming on Multiprocessing". [0]
Applicative programming is an older term for functional programming[1], but note this isn't pure functional programming like in Haskell; it's functional programming like in Scheme and Javascript.
[0] I can't find a pdf of the book, but it was mentioned here https://en.wikipedia.org/wiki/Futures_and_promises - the book calls it promises
[1] https://en.wikipedia.org/wiki/Applicative_programming_langua...
Re:Why is learning functional programming so damned hard? (2...
by dragonwriter on Friday August 20, 2021 @10:15AM
(#28246241)
> Futures were first proposed in 1976, in a book called "The Impact of Applicative Programming on Multiprocessing".
According to Wikipedia, Promises were, Futures (which are similar but not identical) were proposed in a 1977 paper. All of the closely related concepts of promises, futures, logic variables, and dataflow variables were used in functional languages first, and long before their use in, or the existence of, Twisted.