MSDN Channel 9’s Rx videos
Quick Notes on Yesterday’s Post
Within hours of yesterday's post, I had some new information to consider.
Combine: Where’s the Beef?
Let's start discussing Apple's Combine framework by discussing what's missing
Building Up to Combine
Apple has released their take on RxSwift. In order to understand it, one must start from the beginning.
RxSwift to Apple’s Combine “Cheat Sheet”
Get started with Apple’s Combine with your existing RxSwift knowledge
observeOn vs. subscribeOn
How to subscribe and observe on different threads
What’s new in RxSwift 5
Learn about the updated and changes in RxSwift 5, the latest major release of the Reactive Programming library.
Navigation w/ Rx
At Grailed we’ve started using RxSwift and functional programming to simplify our navigation.
Expert to Expert: Brian Beckman and Erik Meijer - Inside the .NET Reactive Framework (Rx)
Cross posted from http://channel9.msdn.com/Shows/Going+Deep/Expert-to-Expert-Brian-Beckman-and-Erik-Meijer-Inside-the-NET-Reactive-Framework-Rx
Erik Meijer and team (developer Wes Dyer, in particular) have created a profound and beautiful .NET library that will take managed event based programming to new levels. Of course, many of you wish that you could write LINQ expressions over events. Well, now you can thanks to Erik's and Wes Dyer's latest creation, Rx - .NET Reactive Framework. Erik, being a fundamentalist functional theoritician, can't create new programming abstractions without employing some form of monadic magic.
Enter astrophysicist and monadic composition wizard Brian Beckman. The last time Brian was on C9 he taught us about the State Monad. At the end of that discussion he mentioned he wanted to teach us about the Continuation Monad next. So, who better to conduct this episode of Expert to Expert than Dr. Beckman? Yep. You guessed it! Rx employs the Continuation Monad in its composition. Erik is in the hot seat this time and it's always a real pleasure to converse with Erik and Brian in the same room at the same whiteboard.
Now, what is Rx?
The .NET Reactive Framework (Rx) is the mathematical dual of LINQ to Objects. It consists of a pair of interfaces IObserver/IObservable that represent push-based, or observable, collections, plus a library of extension methods that implement the LINQ Standard Query Operators and other useful stream transformation functions.
Observable collections capture the essence of the well-known subject/observer design pattern, and are tremendously useful for dealing with event-based and asynchronous programming, i.e. AJAX-style applications. For example, here is the prototypical Dictionary Suggest written using LINQ query comprehensions over observable collections:
Please subscribe to this Channel 9 interview to be notified when we have clearance to distribute Rx over the counter (lame puns intended Smiley.
Tune in. This should prove to be an instant classic besides being a very important episode of E2E. Rx is deep, man. Deep.
Enjoy!
Anatomy of an RxSwift View Model
Recommendations for effective view models when working with RxSwift.
Comparing Reactive and Traditional
It’s a collection of small functions and properties without a linear story. Part of me does not want to encourage people to use RxSwift for the reasons I’ve outlined. But part of me very much wants to encourage people to use RxSwift — because change comes, in part, from the community pushing the state of the art. But if you do use it, and some time in the future there’s a nice, declarative way of handling events and dealing with state, then I’ll have you to thank for helping make that come true.
Waiting On You
Younger self and FRP
RxSwift & MVVM: Your First Steps - YouTube
RxSwift & MVVM: Your First Steps by Shai Mishali
(Hebrew, english Subs available)
Come and learn how to get started with RxSwift and MVVM. What _is really_ an architecture, and what MVVM aims to solve over the standard usage of MVC? Why is RxSwift such a wonderful companion for employing MVVM? Learn all this and more, in this talk.
This presentation also includes actual live coding for building a basic MVVM-based login screen.
Slides at: https://speakerdeck.com/freak4pc/rxswift-and-mvvm-your-first-steps
You can reach Shai as freak4pc on Twitter, GitHub and Gmail.
https://twitter.com/freak4pc
https://github.com/freak4pc
RxSwift/Traits.md
Reactive Programming in Swift. Contribute to ReactiveX/RxSwift development by creating an account on GitHub.
RxSwift: share()-ing is Caring
RxSwift resource sharing can be hard. Learn about share(), which lets you define streams that share resources among their subscribers.
RxSwift: Debunking the Myth of Hard
RxSwift has been one of the most prominent and upcoming frameworks in the iOS & Swift community in the past years. Its usage is becoming widespread and popular with many companies moving their code base to the Reactive world across iOS, Android, Web and Backend - making it a valuable skill to comprehend.
Along with that fact thought, it seems the learning curve for RxSwift and Rx in general always seems "hard" to most people, or too hard to get started with. In this lecture I hope to debunk the myth and misconception of RxSwift being a hard concept, and put developers on the right path to start building Reactive Mobile applications for the modern world.
https://twitter.com/freak4pc
https://swiftconf.com
https://twitter.com/swiftconf
Hot and Cold Observables
Reactive Programming in Swift. Contribute to ReactiveX/RxSwift development by creating an account on GitHub.
Modeling Your View Models as Functions
At Grailed we’ve turned to functional programming for inspiration on how to write testable, well-structured view models.
Stepping Outside My Comfort Zone
I'm dipping my toe into screencasts. Here's my first attempt.
RxSwift Primer: Part 5
Even though it’s a steep learning curve, and it requires rewiring your brain to think about problems differently
RxSwift Primer: Part 4
In the fourth installment of my RxSwift primer, I'll introduce Drivers.
RxSwift Primer: Part 3
In the third installment of my RxSwift primer, I'm starting to show why Rx is so great.
RxSwift Primer: Part 1
it’s likely that the iOS team can crib their solution, platform differences aside. That’s very powerful, as it leads to us all speaking a common language, even though our actual languages are very different.
RxSwift Primer: Part 2
The first step to converting this to use Rx is to think of what the inputs and outputs are. What causes things to happen? What causes us to do a computation, or change what we present to the user?