SwiftUI... but why?

Is it just me, or does anybody else feel like SwiftUI is a new language built by an engineer who didn't realize there are storyboards or how to use storyboards?

I am watching these videos about "how magical it is" to use SwiftUI, then watching an engineer type in code to draw views and cells... Magical in what way? that he is able to recall from memory the code to type in?

I kept thinking, but... but... I can just drag in a view in a storyboard, move it around play with it there as a graphical interface... which actually is magical, I can drag a table view in, and a cell view in and actually stretch it and move it to what I want... drag an image in or a thumbnail view in and size it graphically, where this engineer decided going to menus to find aspect ratios that suspiciously look like what a Storyboards menu views look like.

so why didn't another set of engineers also create the "preview" and tying data structures to storyboards? then call it "meta magical"

now we have an entire new set of language syntax to do exactly the same thing that swift can do? what in the world sense is that? Swift is barely several years old, and now we have to learn a new set of different syntax? and that is if we want to type everything, as this engineer apparently decided that was easier than the "preview" view and dragging stuff in there... (just like from the storyboards by the way) to actually make magic happen? left me wondering if it actually worked by the time the videos were made.

again, where is the magic? typing in syntax out of thin air? I so wanted to ask this engineer to let me build that in a storyboard and show him how to use storyboards... (that was the "but why?") ???

so anyway Apple engineers, how about this, some of you also keep going with Storyboards to be able to hooking in data structures, and live previews and such... (of course this would make SwiftUI sort of.... well extra for no reason, so I am not going to hold my breath) I guess it would depend on who has more pull at Apple; The Storyboard/Xib people who probably all retired rich for doing a great job so no longer there to say (but... but...), or the new engineers who apparently didn't know storyboards existed? and came from some dark room where typing in syntax is cool... (cough) msft/engineering schools who have never seen Xcode/xib/Storyboards (uncough)

or is Apple about to abandon Swift too?

so anyway Apple engineers, how about this

Interesting comments, however, as forum posts are not bug reports (and you're mainly talking to other devs here), feel free to make enhancement requests against the tools via the feedback/bug link below, being sure to add your report #s to your thread for ref., thanks and good luck.
I think you miss the point of SwiftUI. The main benefit of SwiftUI is that your UI is the output of a function where the input is the state you want to display. I cannot think of a better way to solve this problem.

The bad part of SwiftUI is, that it is not mature enough to replace UIKit - but it will be in some years.
I'm not a big fan (yet) of SwiftUI.

But the goal is to get rid of the need to manage the state of UI "manually" (as ChinChin69) did explain.

However, I find it comes at the expense of some awkward (and may be even more complex in many cases) things like managing @state or @published.

At the end, I find it makes me loose control of the UI design (plus the fact that it is still a development in progress).

But remember, some said the same about OO vs procedural at the beginning… So may be it is the next big step… in 5 years.


SwiftUI... but why?
 
 
Q