You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Congratulations on the release of the new Promise library! It looks great and the implementations seems extremely fast and efficient.
I've read the Benchmark you published and noticed RxSwift is one of the "Compared-against" libraries.
This isn't out of "blind love" of RxSwift (it has its flaws and strengths), but comparing a Promise library to a full-blown Rx implementation seems "unfair" or wrong in its basis.
I'd love to learn why you made the decision to compare against it specifically, since it is entirely not a Promise library at its basis (as opposed to PromiseKit or BrightFutures that specifically provide a solution for the "Promise" problem) .
Regardless, since I think all libraries benchmarked against "Google Promises" would love to improve their performance - I, for one, would appreciate it if you could publish the code you used to benchmark against each of the libraries, just so that developers get full clarity while library developers have the opportunity to find bottlenecks they might fix.
Appreciate your response and thoughts on this matter :)
The text was updated successfully, but these errors were encountered:
I totally agree the comparison with Rx implementation may look odd. The reason it's there in the first place, is because we use RxSwift for several projects at Google and there was an internal request to compare the performance of the two, after we had the initial data for all other popular promises implementations.
To address that request we tried to write performance tests for RxSwift in such a way that they would imitate A+-style promises as close as possible, so we had to use Subjects. Using any other type of Observable lead to 2x and more performance downgrade in our experience.
Congratulations on the release of the new Promise library! It looks great and the implementations seems extremely fast and efficient.
I've read the Benchmark you published and noticed RxSwift is one of the "Compared-against" libraries.
This isn't out of "blind love" of RxSwift (it has its flaws and strengths), but comparing a Promise library to a full-blown Rx implementation seems "unfair" or wrong in its basis.
I'd love to learn why you made the decision to compare against it specifically, since it is entirely not a Promise library at its basis (as opposed to PromiseKit or BrightFutures that specifically provide a solution for the "Promise" problem) .
Regardless, since I think all libraries benchmarked against "Google Promises" would love to improve their performance - I, for one, would appreciate it if you could publish the code you used to benchmark against each of the libraries, just so that developers get full clarity while library developers have the opportunity to find bottlenecks they might fix.
Appreciate your response and thoughts on this matter :)
The text was updated successfully, but these errors were encountered: