swiftaccount1

4 ms·

1. 1.▲
   by swiftaccount1 5y ago

   I basically agree with you, actually. It feels like a lot of this is breaking down into semantics. I’m not fond of acronyms, I believe it’s important to go to core principles and never do anything blindly, but only when it’s useful. The fun
2. 2.▲
   by swiftaccount1 5y ago

   Yeah, sorry for the choice of words; I just fired something off with no editing. In my mind, I was thinking of MVC at it's worst (which is unfortunately common). That being said, would love to learn more about how you structure code. W
3. 3.▲
   by swiftaccount1 5y ago

   I'm not sure if I fully agree with that. It's true that you can spaghetti with any pattern, but I think on multi dev teams it helps to have guidelines about what goes where to ensure a clear separation of responsibilities. Someone
4. 4.▲
   by swiftaccount1 5y ago

   That's an interesting article. I find iOS architecture fascinating and spend a lot of time thinking about it. It seems like "MVC" in common usage (based on talking to other iOS devs) means spaghetti, but I guess it doesn&#x27
5. 5.▲
   by swiftaccount1 5y ago

   I made a new account just to ask this: 'MVC works really well and scales really well" Is this a joke? Do you have any professional iOS experience? MVC is famous for scaling terribly on iOS and resulting in view controllers with th