History of Promise
- This person wrote a more than adequate and substantial commentary. Below is my summary and additions.
The Promise idea has its origins in an older
The 1997 E language is almost in the same form as Promise is today.
- E (programming language) - Wikipedia Twisted, a network programming framework implemented in Python in 2001, was implemented with reference to the E language
- It was called Deferred.
- Twisted - Wikipedia
MochiKit, a lightweight JavaScript library, was implemented in 2005 with reference to Twisted
- at that timeXMLHttpRequest - Web APIs | MDNが使われていた、今のfetchに慣れた人からするとすごくめんどくさい
- The intent was to make this easier.
- MochiKit - Wikipedia
Dojo, Q, and a number of other JavaScript libraries began to adopt similar concepts, and jQuery did so in 2010.
- Dojo Toolkit - Wikipedia
- Q
- jQuery was at least for a time a very major JavaScript library
- The air of someone who doesn't know much about it and uses it anyway.
- jQuery has allowed "this way of doing things" to spread to a wide range of JavaScript programmers.
A unified test case Promises/A+ was created, and the mixed implementations of "this way of doing things" became "Promise implementations that behave the same".
- This also helped standardization by objectively demonstrating that a single concept of "Promise" is used in a wide range
It was then standardized in 2015 in the form of ES2015.
This page is auto-translated from /nishio/Promiseの歴史 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.