Some nice background on how/why things went all reactive on us.
I’ve been trying to understand the Elm Architecture for a new iOS project. I kept reading over this article and thinking, “Wait a minute…. What’s the catch here? This seems too simple.” 🧐
I like that this architecture can be explained in a very short post with examples.
The beauty of The Elm Architecture lies in its simplicity.
That article is simple but assumes a web UI and explicit mentions HTML 🙄. Here is a funnier and more useful article about Elm for iOS. 😂
Elm architecture can be described as follows
msg -> Model -> View -> msg
I even made my own diagram just to make sure I “got” it. The devil is in the details, but I think this is right. 🤷🏻♂️ It definitely seems simpler than VIPER.
I liked his approach of starting with the very simplest way of using Combine to process downloaded JSON data, before moving on to splitting tasks into more logical chunks with chaining.
The latest iOS Dev Weekly had some great links to Combine resources.
This looks really useful as I get into Combine and reactive iOS programming.
Also, this for, well, understanding Combine.
Thanks as always, iOS Dev Weekly!
Free open source Xcode Instruments plugin for profiling reactive Swift code, wither RxSwift or Combine. How is this stuff free?!?
Timelane is a free app that bundles a custom Xcode Instrument and the frameworks to enable your code to talk to the Timelane instrument.
Via iOS Dev Weekly.
ReactiveX is a combination of the best ideas from the Observer pattern, the Iterator pattern, and functional programming
And don’t forget RXMarbles for some experimenting with Rx.