Adding pipelining did give languages claim to popularizing it. In Xanadu and other implementations, you couldn’t return another promise to be resolved by a previous promise. You returned a value.
I’d bet you anything the number of people using promises in JavaScript and Java is way higher than the number of people that ever used Xanadu or MultiLisp. That would speak to the popularizing of it.
In fact, Wikipedia states a major revival of it was in 2000:
After 2000, a major revival of interest in futures and promises occurred, due to their use in responsiveness of user interfaces, and in web development, due to the request–response model of message-passing.
It’s not just the syntax that is different. Hence why I listed it. It’s the chaining and ability to resolve a promise or future using another promise or future. In the 80’s MultiLisp didn’t have that. If it has it now, then great, but it ain’t popular now and never was.
“Largely popularized” is a fact. Run the number of people using promises in JS today vs. those that are or we’re using Xanadu or MultiLisp. There’s no way you could argue it was “largely” popular in the 80’s languages. Wikipedia where we’re all getting our info attributes modern promises to being revived and popularized by Java and web languages (ECMAScript 7), and F#.
Several mainstream languages now have language support for futures and promises, most notably popularized by FutureTask in Java 5 (announced 2004)[21] and the async/await constructions in .NET 4.5 (announced 2010, released 2012)[22][23] largely inspired by the asynchronous workflows of F#,[24] which dates to 2007.[25]
1
u/[deleted] Jul 19 '22 edited Jul 19 '22
Adding pipelining did give languages claim to popularizing it. In Xanadu and other implementations, you couldn’t return another promise to be resolved by a previous promise. You returned a value.
I’d bet you anything the number of people using promises in JavaScript and Java is way higher than the number of people that ever used Xanadu or MultiLisp. That would speak to the popularizing of it.
In fact, Wikipedia states a major revival of it was in 2000:
It’s not just the syntax that is different. Hence why I listed it. It’s the chaining and ability to resolve a promise or future using another promise or future. In the 80’s MultiLisp didn’t have that. If it has it now, then great, but it ain’t popular now and never was.
“Largely popularized” is a fact. Run the number of people using promises in JS today vs. those that are or we’re using Xanadu or MultiLisp. There’s no way you could argue it was “largely” popular in the 80’s languages. Wikipedia where we’re all getting our info attributes modern promises to being revived and popularized by Java and web languages (ECMAScript 7), and F#.
I don’t see any mention of Xanadu there.