FRP and RxSwift Core Logic

Talk about FRP

FRP(Functional Reactive Programming) is a programming paradigm for reactive programming (asynchronous dataflow programming) using the building blocks of functional programming. 

Let's talk about functional programming first. Functions are treated first class and can be parameter or return value.

Why functional programming is popular and what is the advantage?

1. low side effect

2. immutability

3. easy to test

4. generally, more concise

what is pure function?

Pure function always return same value given some input and it has no side effect. that is why it is easier to test and safer. As we know all operation related IO will cause side effect, and increase the system complexity and uncertainty. In a function with side effects, the function depends on or changes the state of the outside world, this would increase the difficulty of the testing and mess up the whole system. So functional programming promotes immutability. 

Always try to use immutable first in the practice. this is the same idea why swift recommend to use struct vs class. When there are multiple threads running in the system, immutable or constant would keep you safe, obviously. 

Function is the abstract of the world, in the complex system theory, y = f(a, b, c ...). Hence, most of the use cases, functions can represent the model of the bossiness logic and generally more concise. We can use swift to write quick sort in three to four lines:

func quicksort<T: Comparable>(_ a: [T]) -> [T] {

  guard a.count > 1 else { return a }

  let pivot = a[a.count/2]

  let less = a.filter { $0 < pivot }

  let equal = a.filter { $0 == pivot }

  let greater = a.filter { $0 > pivot }

  return quicksort(less) + equal + quicksort(greater)

}

And let us talk about Reactive Programming.

In my view, Reactive Programming is just a programming paradigm for the event handling and it is based on observer pattern.

Generally, when we design a system, we need to think about the event handling or event bus. In deep it is the art about passing information.

In iOS, normally there several ways to pass values.

1. Direct message. 

let vc = UIViewController()

vc.title = "My"    

this is the most direct way, people even cannot tell it when asked in a interview. But it is a powerful way. with a good design and clean code , you can use it to solve most of the use cases.

2. Notification

broadcast information is powerful however it could impact performance and could be messy

3. delegation 

Heavily been used in UIKit and could be messy. actually it is just callback.

4. target/action

Heavily been used in UIControl, based on OC dynamic feature.

5. KVO

could be replaced by Swift didSet feature.

6. block/closure/callback

Swift make functional more comfortable to use. however, could easily get a callback hell, especially in asynchronous programming.


And when there is heavily realtime UI event, the code could be complex. Hence Reactive programming, which has higher level abstract ability, focus more on the event / signal / stream/ sequence / observable, and their dependencies, to make front end business more clear and easy to write.

What is RP methodology ?

Keynotes about RP

1. Everything is event / signal / stream/ sequence / observable

2. React to event / signal / stream/ sequence / observable

3. Introduce one way bind and mutual way bind to iOS, this is normally a basic in front end technology.

4. signal could be combined and processed 

5. Create observable -> Observer Subscribe -> Send signal

I reference a diagram to show the idea of the RP


reference: https://gist.github.com/staltz/868e7e9bc2a7b8c1f754#file-zmulticlickstream-png

RxCocoa example

       textField.rx.text.orEmpty.subscribe(onNext: { (text) in   print(text)  }).disposed(by: disposeBag)


let us step into rx source code to see how the event handler could be executed.


RxSwift example

    let ob =Observable.create{ (observer) ->Disposable in

            observer.onNext([1,2,3,4])

            observer.onCompleted()

            returnDisposables.create()

       }

            let_= ob.subscribe(onNext: { (text)in

                print("\(text)")

            })

When Create Observable, It creates AnonymousObservable: 


When observer subscribe, it create AnonymousObserver


reference from: https://www.jianshu.com/p/0e0703466483
最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 216,240评论 6 498
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 92,328评论 3 392
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 162,182评论 0 353
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 58,121评论 1 292
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 67,135评论 6 388
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 51,093评论 1 295
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 40,013评论 3 417
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 38,854评论 0 273
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 45,295评论 1 310
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 37,513评论 2 332
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 39,678评论 1 348
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 35,398评论 5 343
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 40,989评论 3 325
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 31,636评论 0 22
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 32,801评论 1 268
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 47,657评论 2 368
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 44,558评论 2 352

推荐阅读更多精彩内容