MVVM is BAD for SwiftUI - Use MVC Instead! (Yes, MVC) 

Stop using Spacer in SwiftUI (and what to use instead) 👉 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-S6bufNjIteQ.html&ab_channel=Rebeloper-RebelDeveloper

Thanks for the video. However, you only renamed VM to Controller and moved it in root view. The only point of this video was only a renaming!

Thanks for your videos. There is a big But here. If you define a Controller (ViewModel) as an Environment object, it will always exist in memory. while when you are creating views and mentioning a ViewModel as @StateObject (you add @State, which is wrong for defining a ViewModel or controllers), it will be deinitialized when the view is destroyed. So for enterprise projects, it is a very bad way to create Controllers(ViewModels) as an environment object.

so if UserController was renamed UserViewModel how is that any different than MVVM?

I think people are already using mvc like when passing data through screens we initialise in the main file and pass it as environment .

Correct me if I'm wrong, but it's an easier way to Composition Root? I do it in UIKit creating factories in the AppDelegate, it's the same effect?

Hi, like you explanation, sure you are going to receive a lot of comments regarding the importance of MVVM because for large projects, and stuff like that. At the end I really support your comments regarding that no problem in put Business logic in the View, because at the end the MMVM file it has to be related to the view so not difference. You approach to use MVC is great.

I totally disagree

It's MV architecture. NOT MVC!

MVVM is garbage