I just learnt that @EnvironmentObject does what @ObservedObject can do, but easier, so why use it ?

I understand that @StateObject doesn't force the data to reload like @ObservedObject can, but unsure about @EnvironmentObject. If not, then why would a developer bother with the hassle of typing the extra code ?

Is that that resouce intensive to use @EnvironmentObject ?

Check out this post What’s the difference between @ObservedObject, @State, and @EnvironmentObject?.

Note: that this acticle was written September 3rd 2021 and now use @Environment and @Observable.

Sharing SwiftUI state with @Observable

I saw the changes in iOS17, I appreciate the streamlining.

However, why use the term "environment" ? The term Statement isn't use, it's State, so why not Environ ?

Think it @Environment because an object going into the setting(environment) of OS and can be access anywhere in the app, as where @State is a state of object in a View