Using Future

I will try to explore concept of Async state and Future monad

1. USING FUTURES @daloog
2. ABOUT skype: nobidon dalog@me.com https://speakerdeck.com/dalog
3. ASYNC VS PARALLEL
4. ASYNC DO THINGS AT DEFERENT TIME
5. PARALLEL DO THINGS AT THE SAME TIME
6. GCD
7. GCD
8. NSOPERATION
9. NSOPERATION
10. [ _ TARGET: ACTION: ]
11. DELEGATE
12. STRATEGY AND CALLBACK
13. BLOCK
14. CALLBACK!!!
15. SIGNATURE DANCE
26. SEPARATE WORK FROM RESULT DELIVERY
27. SETTER
28. T -> ()
29. GETTER
30. () -> T
31. T -> U IS (GET, SET) -> ()
32. T -> U (() -> T, U -> ()) -> ()
34. ASYNC?
35. ASYNC GETTER
36. () -> T (T -> ()) -> () SET -> ()
37. SET<T> -> () FUTURE<T>
38. ASYNC SETTER
39. T -> () () -> (T -> ()) () -> SET
40. () -> SET<T> PROMISE<T>
41. GETTER + SETTER = STATE
42. PROMISE + FUTURE = ASYNC STATE
43. ASYNC STATE >>> STATE
44. WHY THIS IS SO HARD???
45. ACTUALLY NOT
46. THINK ABOUT FUTURE AS A BOX
47. BOX WILL BE OPENED. SOMEDAY. MAYBE.
48. A = B C = A
49. CHAIN?
50. T -> U U -> K T -> K
51. T -> F<U>
 U -> F<K> T -> F<K>
52. (F<U> , U -> F<K>) -> F<K>
53. AND THEN
54. FLAT MAP
55. ERROR?
56. TRY<T, E>
57. FUTURE<T, E> = FUTURE<TRY<T, E>>
58. WHAT CAN BE FUTURE?
59. ANYTHING
60. UI
61. USING FUTURES FOR REVERSING UI FLOW. HTTPS://MEDIUM.COM/P/D3F5B7CA32D9/ EDIT
62. VM -> F<ACTION>
63. NETWORK BLUETOOTH …
64. EXPOSE F<> AS PUBLIC API
65. ALWAYS
66. USE ANY LIB • https://github.com/BoltsFramework/Bolts-iOS • https://github.com/mxcl/PromiseKit • https://github.com/Thomvis/BrightFutures • https://realm.io/news/swift-summit-javier-soto-futures/ • https://realm.io/news/swift-tasks-nevyn-bengtsson/
67. ALL LIBS EQUAL ITS JUST ASYNC STATE
68. FUTURE / PROMISE ASYNC GET/SET