Open flowtoolz opened 5 years ago
Promises are not similar to a reactive framework. Promises are for one time operations, combine is for continuous changes from model to data layer. I don’t see them having any overlap. PromiseKit will exist until Swift gets an async language feature.
Thanks for the answer :)
I thought where the overlap might come is that Combine would be able to handle those one shot callbacks as well, like through this: https://developer.apple.com/documentation/combine/publishers/future
Didn’t know about that. Well maybe PMK is dead then. Each individual user can make their own decision.
PMK is certainly not dead. I feel it's simpler, easier to write, more pleasant to read, more focused and comes from its own angle. I'm just curious how both could complement each other. Maybe it makes sense to build Combine extensions for Promises, or the other way around, I have neither your depth of knowledge nor conceptual overview on this...
Thanks for the answer :)
I thought where the overlap might come is that Combine would be able to handle those one shot callbacks as well, like through this: https://developer.apple.com/documentation/combine/publishers/future
The link is dead
Thanks for the answer :) I thought where the overlap might come is that Combine would be able to handle those one shot callbacks as well, like through this: https://developer.apple.com/documentation/combine/publishers/future
The link is dead lol :P
Promises are not similar to a reactive framework. Promises are for one time operations, combine is for continuous changes from model to data layer. I don’t see them having any overlap. ### PromiseKit will exist until Swift gets an async language feature.
https://docs.swift.org/swift-book/LanguageGuide/Concurrency.html
With SwiftUI comes the full fledged reactive framework "Combine". Does this have any implications for PromiseKit? And what do you think of Combine?