<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Reactive programming is still catching on and evolving on the various platforms.Typically once you standardize something it must evolve drastically slower, so it works out better if mature technologies are pulled in.</div><div class=""><br class=""></div><div class="">I wouldn’t mind eventually seeing something analogous to <a href="http://www.reactive-streams.org" class="">http://www.reactive-streams.org</a> in Swift. Reactive streams takes a step beyond most of the other reactive framework APIs and adds back pressure support. These API were driven by consensus between many projects on having a common base set of interfaces for implementation, and are being incorporated into the Java 9 release as well (as java.util.concurrent.Flow).</div><div class=""><br class=""></div><div class="">Right now I don’t think the various reactive programming libraries for objective-C and swift are close to having consensus on a baseline set of protocols, so I would imagine standardizing reactive programming would mean either picking a winner or adding yet another competitor to the mix.</div><div class=""><br class=""></div><div class="">-DW.</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On May 10, 2016, at 1:41 AM, James Campbell via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">With swift 3 around the corner, I wanted to propose some higher level focuses for version 4.</div><div class=""><br class=""></div><div class="">My first suggestion is an official reactive library. Reactive programming has gained a huge amount of popularity especially with reactive cocoa and rxswift.</div><div class=""><br class=""></div><div class="">Microsofts support of the original Rx library is a big help in this. </div><div class=""><br class=""></div><div class="">I believe the apple ecosystem would benefit from offering this same support to an official library, why?</div><div class=""><br class=""></div><div class="">- RxSwift in particular is pushing the limits of the compiler and often crashes source kit. I believe if we had an official library we could have tighter feedback to the compiler team.</div><div class="">- it would help address the complexities of async code without reinventing the wheel.</div><div class="">- it could reduce app size. RxSwift is a large framework right now but I would imagine with the right system knowledge it could be refined and the API simplified with an official library.</div><div class=""><br class=""></div><div class="">Let me know your thoughts</div><div class=""><br class=""><div class="acompli_signature">Sent from <a dir="ltr" href="http://supmenow.com/" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="0" class="">Supmenow.com</a></div><br class=""></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>