Coordinators - Soroush Khanlou

[@Tracks777]

Good video! Keep it up!

[@mukulbakshi28]

Its not for very large scale apps in that case we have at last a massive coordinator with lot of extensions of different controllers and one more thing thinking about the principle of separation of concern while push from one vc to next controller while passing the dependency and in both way then it make it really difficult to manage when b controller passes the data to a.

[@edwardsamson1677]

You can always break up larger coordinators into multiple smaller coordinators to avoid massive coordinators. Though I do agree that passing data can be kind of tricky and I haven't figured out a clean way to do it in all cases.

[@sacredgeometry]

The controller is a light weight arbitrator between the views and the app state. Everything that has to do with app logic that isn't related to views (whilst technically is part of the model) doesn't even need to be considered as part of the MVC pattern. It's a UI design pattern first. Not an application architecture. I am lost why sticking view controller logic in a view controller is problematic because it makes them large? Good organisation of code, encapsulation, extensions, composition, inheritance etc allows you to mitigate that. Im not entirely sure how its relevant to the coordinator pattern either which I thought was predominantly a pattern to allow for cleaner decoupling of view controllers.

[@sacredgeometry]

In response to 6:56 That's definitely a model.