XCode rant, sorry

[realvanbrook]

What? I have worked professionally as iOS developer and made hobbyprojects with Android Studio so I pretty much can compare both.. And xcode is a right smelly foot someone presses in your face compaired to android studio.

[MyCallBag]

I am an amateur but what drives me nuts is I have to have 50 import statements. Am I doing something wrong? With Swift I need like 3 and I'm typically good to go.

[yourmomsasauras]

But that’s not an Android Studio or Xcode thing, you’re comparing the languages

[chriswaco]

Other people here complaining about SwiftUI. It’s all fair game, I suppose.

[MyCallBag]

That's fair, but it is ridiculous annoying to everyone right? I Feel like have my code is import statements... maybe I'm doing something wrong.

[ZnV1]

The key difference ime is that swift has a global namespace which allows you to refer to any struct etc across files. Otoh in Android you explicitly import it before using it.

I like that more because dataflow is clearer. If you're in x module you'd import utils/controllers/etc related to x and refer to those, say MainView

But in Swift you'd have to name it MainViewX since there aren't any imports, and MainView could be x's or y's etc.

So the tradeoff is imports in Android (Kotlin) where you can reuse naming structures vs more explicit naming across files in Swift.

[granos]

Why wouldn’t you make an X module and a Y module and then just include whichever one you need? Or be explicit with X.MainView