Live data from Hacker News

SwiftUI

developer.apple.com

191–200 of 394 posts

Re: SwiftUI

#191
post #19
post #3

To me this looks very similar to what Google is doing with Flutter.

Jetpack Composer you mean. I bet by next IO, Flutter will get replaced by it, specially after the #KotlinEverywhere announcement and Kotlin/Native effort for iOS.

It looks like Jetpack Compose is not really done yet. It's pre-alpha and the Jetpack Compose doc page says don't use it for production. https://developer.android.com/jetpack/compose/

I may be missing something, but SwiftUI seems to be pretty much ready to go today.

Re: SwiftUI

#193
post #67

The syntax example is still not as clean as QML, which is already a ten-year-old language (examples: http://qmlbook.github.io/ch04-qmlstart/qmlstart.html ).

But it is Swift, which (at the risk of stating the obvious) QML is not. And you can't write an entire app in QML. There's something to be said for being able to use one language for all things.

Well, you can almost surely write entire apps in QML if you take the C++ entrypoint for granted.

Just a couple examples: you can do Bluetooth discovery scans in QML without writing any C++ [1], you can read from ~20 sensors without writing any C++ [2], you can write complete 3D scenes declaratively in QML [3], and the list goes on.

[1] https://doc.qt.io/qt-5/qml-qtbluetooth-bluetoothdiscoverymod...

[2] https://doc.qt.io/qt-5/qtsensors-qmlmodule.html

[3] https://doc.qt.io/qt-5/qt3d-wireframe-example.html

Re: SwiftUI

#194

Other than a few-hour intro seminar on building iOS apps, almost 10 years ago, I've never written anything in Swift. The announcements around it today got the biggest reactions from the crowd. Is is really great, blasé, or too early to tell?

You were not using Swift 10 years ago, or even almost 10 years ago. It was released in 2014.

Re: SwiftUI

#195

The syntax example is still not as clean as QML, which is already a ten-year-old language (examples: http://qmlbook.github.io/ch04-qmlstart/qmlstart.html ).

I don't understand why this gets downvoted. It's an entirely valid point and probably SwiftUI took inspiration from it.

Re: SwiftUI

#196
post #180

Earlier quoted context omitted.

Nope, iOS13 is required, as SwiftUI is a system framework.

So I guess macOS 10.15 too, yes?

According to the documentation the latest OS release is required on all platforms SwiftUI targets.

Re: SwiftUI

#197
post #192

Does the syntax sort of kind of remind anyone else of Shoes?[1] http://shoesrb.com/

Yes, I wonder what framework Apple engineers looked at for inspiration, and if they looked at shoes. Although I doubt they are allowed to answer this question.

Re: SwiftUI

#198

I’m one of the engineers that spearheaded this initiative inside of Apple. I just wanted to thank the HN community—I’ve been reading HN for 10 years now and it’s been formative in my development as a software engineer. If you’re at WWDC stop by the labs and say hi!

This looks fantastic, congrats! Any word on whether 3rd party IDEs will be able to integrate the live-preview functionality? (AppCode user)

I assume AppCode will support this the same way it does with InterfaceBuilder and Storyboards - i.e. it won’t do anything but launch XCode to handle it.

Re: SwiftUI

#199
post #9

I hope it still supports low-level control when you need it.

Well the docs say you can chain an id() property on any view being built in the tree which would hopefully allow you to reference it at runtime and insert/delete children, but I don't see anything obvious for assigning that id to like an outlet so you don't have to traverse the whole tree to find it.

Re: SwiftUI

#200
post #29
post #19

Earlier quoted context omitted.

Jetpack Composer you mean. I bet by next IO, Flutter will get replaced by it, specially after the #KotlinEverywhere announcement and Kotlin/Native effort for iOS.

No he means Flutter which has been around a lot longer, it's immediately what I've thought of being inspired by as well: https://flutter.dev/docs/development/tools/hot-reload

I know pretty much what he/she meant, was just making a point that I don't believe in Flutter's long term success.

Trying to sell Dart a 2nd time was a mistake.

Post reply on HN