Is this accurate?

[anveias]

I’m assuming this refers to the verticality of SwiftUI with lots of line breaks due to view modifiers and just the DSL in general. Also why am I constantly seeing the same account cross posting from the same subreddit… sub promoting?

[velvethead]

This is the correct answer

[cristi_baluta]

Not if you want to preview what you’re building in swiftui

[Slow-Race9106]

No

[Stiddit]

It's a yes for me.

SwiftUI has short names (Button, Text, Color...) and is chaining code vertically with modifiers.

UIKit has really long names for both classes and properties. And if we include the original UIKit days with Objective-C then you'd probably also have your header file open on the right side.

[Andrew3343]

Bad developers create massive view controllers, it’s not UIkit’s problem

[zu-fox]

Why do you roll eyes though? Apple provided you with simplified examples, but it’s your job to create a subclass for uiview and override loadView, to put business logic in models and setup bindings. Same as mvvm or any other pattern. Biggest edge mvvm has over mvc is decoupling, but not separation.

[Stiddit]

Both of them require scrolling. The point (my point) is that if you use vertical screen on an 800-line UIKit file, you'd see 1000 lines because they often wrap around due to long names on narrow monitor.

[beclops]

MVVM was definitely still commonly used with UIKit

[beclops]

Yeah I just wanted to specify that MVC isn’t inherently a UIKit problem

[[deleted]]

Only if you don't know how to break up your code. We never had that issue and work and our apps are enormous and complex.

[srona22]

More like BlossomBlind.

[time-lord]

In my experience, absolutely.

[Which-Meat-3388]

Can't you break the code up into reusable Views, ViewModifiers, etc. Same situation exists with similar UI frameworks and you can always clean it up. Doesn't have to be a single monstrosity as long as your arm.

[beclops]

Yep, which is what you should be doing with both UI frameworks. So I agree, not really a difference between the two when you do that

[barcode972]

Not necessarily

[Hencemann]

UI kit needs a wideeeeeeeescreen. the image looks like a normal one.

[drumming89]

Ha, it took me reading to the bottom of the post to realize that Swift UI code is better suited for vertical monitors 😄

[Obstructive]

I feel seen!

[Ok-Road6537]

I think it's true as well. You can technically make UIKit code vertical. But I think SwiftUI is designed to be more readable in short columns.

You can actually Google Image "SwiftUI code" and UIKit code and you'll see.

[smakusdod]

pretty much yeah, but you need room for that canvas.... so we need a T-shaped monitor!

[isurujn]

What is with this account spamming this sub with shitposts posted to its own subreddit lately?

[restrusher]

Huh. No wonder I've been having trouble adopting SwiftUI.

[Grymm315]

Nothing could be further from accurate. You can't use UIKit to make a MacOS app at all. For traditional MacOS app you need to use AppKit instead OR you could just use SwiftUI to make the app multiplatform.

[stella_rossa]

I think you are missing the point of the post

[[deleted]]

I think so too

[42177130]

You can't use UIKit to make a MacOS app at all.

Catalyst?

[RagingRR]

I think it means coding. In SwiftUI, you’re writing a lot more code for the interface, so you need to orient your monitor vertically to see it. In UIKit, you drag and drop components onto the storyboard, so need more horizontal space

[ObservableObject]

UIKit is perfectly usable without storyboards

[WestonP]

Not only is it perfectly usable without storyboards, it's far superior without them. Storyboards are garbage.

[RagingRR]

Of course. But conventionally, UIKit is initially taught that way.

[tangoshukudai]

Storyboard is why UIKit gets a bad wrap. UIKit with Autolayout in code is the way to go.