我看到Javier Soto的Back to the Futures演示文稿让我对ReactiveCocoa和功能反应编程又名FRP感到兴奋。 Ash Furrow的功能反应真棒随着Swift演示大大帮助说服了我。
截至2015年11月，我使用最新的Xcode和Swift （适用于iOS 8+的Xcode 7.1 Swift 2）。 对于几天内出现的新项目，我想使用ReactiveCocoa或其他一些FRP框架。 但是，支持Swift 2的ReactiveCocoa 4.0尚未准备好生产。 它是阿尔法。 如果我有一个项目可能会在一两个月内使用alpha版本发货，我不知道会发生什么。 如果我使用alpha并使用基础知识，它会不会出现bug，只会偶尔改变api？
如果一个人想在一个月内使用Swift 2和FRP加船，那么这里有什么明智之举？
我现在如何将FRP框架纳入我的新项目中，有哪些风险？
其他FRP框架： RxSwift ， ReactKit
I saw a Back to the Futures presentation by Javier Soto that got me excited about ReactiveCocoa and Functional Reactive Programming aka FRP. Ash Furrow's Functional Reactive Awesomeness With Swift presentation greatly helped convince me as well.
As of Nov 2015, I use the latest Xcode and Swift (Xcode 7.1 Swift 2 for iOS 8+). For a new project coming up in a couple days, I would like to use ReactiveCocoa or some other FRP framework. However, ReactiveCocoa 4.0 that supports Swift 2 is not production ready. It's in alpha. I don't know what to expect if I have a project that I might ship in a month or two using the alpha version. If I use alpha and use the basics, will it be bug free-ish with only api breaking changes now and then?
If one wants to use Swift 2 and FRP plus ship in a month, what's a smart move here?
How can I get a FRP framework into my new project now and what are the risks?
Other FRP frameworks: RxSwift, ReactKit
最满意答案
您可以在此处查看ReactiveCocoa's 4.0版本的待处理问题列表。
除了一些潜在的API更改，以及一个有解决方法的小问题 ， 4.0应该可以用于生产用途（我已经在生产中使用它一段时间了）。
考虑到这一点，我强烈建议去RAC :)
You can see the list of pending issues for ReactiveCocoa's 4.0 release here.
Except for a few potential API changes, and a minor issue which has a workaround, 4.0 should be ready for production use (I've been using it in production for a while myself).
Considering that, I'd strongly suggest going for RAC :)
更多推荐
发布评论