@@rebeloper I found the key to the difference was the fact that MVVM doesn't let you share anything...this is giving me the opportunity to move forward the "Service" concept. I'm not yet sure about the utility thing...but for now I will use the service to manage the database interactions too.
That's the same as MVVM! Honestly, the "U" or utility is just very redundant and you add unnecessary codes, making the codebase less maintainable. Also one more thing, you are using static, which are bad for memory management as they don't get cleaned up, which are bad for ARC.
STOP Using Conditional Modifiers in SwiftUI! Here's What to Do Instead 🚀 th-cam.com/video/mVChmuAaQxo/w-d-xo.html&ab_channel=Rebeloper-RebelDeveloper
Great Vid
The same mvvm, but use another words.
Indeed!
Really?
@@rebeloper I found the key to the difference was the fact that MVVM doesn't let you share anything...this is giving me the opportunity to move forward the "Service" concept. I'm not yet sure about the utility thing...but for now I will use the service to manage the database interactions too.
Where is game changer? What the difference between this and vm?
Honestly none, he just makes the code more polluted making it less maintainable.
That's the same as MVVM! Honestly, the "U" or utility is just very redundant and you add unnecessary codes, making the codebase less maintainable. Also one more thing, you are using static, which are bad for memory management as they don't get cleaned up, which are bad for ARC.
Thanks for the feedback
th-cam.com/video/kw6KZqnXejQ/w-d-xo.html