Very good talk! The only thing I disliked is the is the MVVM-C term (same thing with MVC-N) I really don't see the need for adding lettes to the pattern acronyms every time we incorporate a new pattern og change or architecture, I feel this is what leeds to new developers thinking that in MVC every piece of code should in one of those letters (at least thats what I thought for a long time). If I want a separate network layer in MVVM-C should I start calling it MVVM-C-N ? og just accept that all architecture evolves along with the progress of the app when we learn more about the domain. Architecture is not something that can be condensed into an acronym.
Good stuff. I think the evolution of the Coordinator pattern is one of the most important things happening in iOS/Cocoa right now. A lot of rethinking about basic Cocoa development needs to happen, away from Apple's conception of MVC. (IMO, Segues in Storyboards, while superficially attractive, have been a huge mistake, in terms of project maintainability and architecture.) A big thank you to devs like Krzysztof and Soroush Khanlou for pushing this thinking along.
I’m not 100% convinced the Coordinator pattern as currently defined is the most perfect, but I completely agree Apple’s MVC direction with integrating segues and the whole dependency graph concept tying view controllers together is FUBAR, because your unit of reuse is any given view controller and all the view controllers it can transition down to, recursively. View controllers should be 100% reusable elsewhere in another application with zero modifications to it, so long as you provide data to it and get it from it.
Do you have a link for the "Graph Source" dependency visualiser? I tried to find it but I was successful only with "objc-dependency-visualizer". I would like to get a similar dependency graph as is included in Krzystof's presentation.
Good technical presentation marred by the political bullshit imposed on viewers, thus earning a thumbs down. Tech is tech: keep it only about the tech, don’t inject politics.
Very good talk! The only thing I disliked is the is the MVVM-C term (same thing with MVC-N) I really don't see the need for adding lettes to the pattern acronyms every time we incorporate a new pattern og change or architecture, I feel this is what leeds to new developers thinking that in MVC every piece of code should in one of those letters (at least thats what I thought for a long time). If I want a separate network layer in MVVM-C should I start calling it MVVM-C-N ? og just accept that all architecture evolves along with the progress of the app when we learn more about the domain. Architecture is not something that can be condensed into an acronym.
Great talk! Really like the idea of coordinators!
SIR...Your stuff is so much helpful for the coders like me who are new in this stream
THANK YOU...
Really great talk, thank u for the share
Good stuff.
I think the evolution of the Coordinator pattern is one of the most important things happening in iOS/Cocoa right now. A lot of rethinking about basic Cocoa development needs to happen, away from Apple's conception of MVC. (IMO, Segues in Storyboards, while superficially attractive, have been a huge mistake, in terms of project maintainability and architecture.)
A big thank you to devs like Krzysztof and Soroush Khanlou for pushing this thinking along.
I’m not 100% convinced the Coordinator pattern as currently defined is the most perfect, but I completely agree Apple’s MVC direction with integrating segues and the whole dependency graph concept tying view controllers together is FUBAR, because your unit of reuse is any given view controller and all the view controllers it can transition down to, recursively. View controllers should be 100% reusable elsewhere in another application with zero modifications to it, so long as you provide data to it and get it from it.
Well done Krzysztof!
Great presentation. Thank you
Excellent. Help me with my app, haha, I am near the NYT building...
Great video, thank you very much!
Do you have a link for the "Graph Source" dependency visualiser? I tried to find it but I was successful only with "objc-dependency-visualizer". I would like to get a similar dependency graph as is included in Krzystof's presentation.
awesome thanks
Good technical presentation marred by the political bullshit imposed on viewers, thus earning a thumbs down.
Tech is tech: keep it only about the tech, don’t inject politics.
Strict NonConformist lol