To me this looks very similar to what Google is doing with Flutter.
But native, of course.
And proprietary.
SwiftUI
121–130 of 394 posts
Re: SwiftUI
#122I'm laughing at all the handwringing over Marzipan in the lead-up to this year's WWDC. The future of MacOS development is not Marzipan and never was. The future is SwiftUI.
SwiftUI running through Catalyst, surely?
Or maybe Catalyst runs on (in?) SwiftUI?
@kylemacomber - can you provide some context here? I'm sure many of us would love to get a high-level understanding of this.
Re: SwiftUI
#123Earlier quoted context omitted.
https://developer.apple.com/download/
Thank you, but that's how far I got myself. It is telling me there are no downloads available at this time. I am asking, because I am still on 10.14.5 and I thought the Xcode 11 beta might only be available on the 10.15 beta.
The XCode 11 "whats new" page [0] says:
>To use the SwiftUI design canvas Xcode 11 must running on macOS Catalina.
Please let us know if you find that's incorrect.
Re: SwiftUI
#124Earlier quoted context omitted.
Why would Apple want these apps to run in Safari? They have a platform to run these already.
Safari isn't the point -- running on other platforms is. Market share for iOS globally is nowhere close to Android; in India iOS is only about 10% so if your SwiftUI app could run in Chrome on Android and is installable as a PWA, you open up the rest of the handset market.
Apple doesn’t really care about you being able to run your UI code on those platforms.
Re: SwiftUI
#125I'm laughing at all the handwringing over Marzipan in the lead-up to this year's WWDC. The future of MacOS development is not Marzipan and never was. The future is SwiftUI.
SwiftUI running through Catalyst, surely?
SwiftUI isn't confined to Catalyst. It's available to native Mac AppKit apps as well as UIKit apps.
(At least it appears that way, going by the WWDC session descriptions. We'll know more in a couple of hours)
Re: SwiftUI
#126Reminds of Visual Basic, seriously nothing is even close to an invention there. It has been forever since Apple development experience is the most crappy and unproductive of all other languages.
The least they should do is replacing this shit Xcode, and allowing other company to build better IDE and language tooling for swift or whatever.
Re: SwiftUI
#127I didn't catch it. Is Xcode 11 (beta) available already? Do I need macOS Catalina (beta) to run it? I seem to have missed the crucial information and cannot find it on apples developers pages...
The direct download is here:
https://developer.apple.com/services-account/download?path=/...
for some reason my account only shows "There’s currently no beta software available for download."
Re: SwiftUI
#128Do the trailing closures implicitly return arrays of child elements? Or what kind of syntax is that?
Single-expression functions can now return a value without the “return” keyword: https://github.com/apple/swift-evolution/blob/master/proposa...
Yeah but the example code looks like multiple expressions?
Re: SwiftUI
#129I'd be curious to know how many React Native devs work on cross-platform apps. In casual conversation I've had it actually isn't that high, despite it being one of the central promises of RN. Given that SwiftUI has live reloading and a sensible template interface I could absolutely see it winning over some RN devs. There's something to be said (particularly with Apple) for using the native toolset rather than RN, Flu…
> In casual conversation I've had it actually isn't that high, despite it being one of the central promises of RN. But applications written in React Native aren't cross platform, are they? You have different components depending on the platform. My understanding is that they claimed you wouldn't have to learn a different framework when switching to a new platform, not that your apps would be portable.
I built cross-platform apps with it.
It works by supplying me with native modules and native components for every platform and I write my domain logic in portable JavaScript.
Re: SwiftUI
#130Earlier quoted context omitted.
@State var model = Themes.listModel I haven't tried it out, but the above looks more like MobX: @observable model = new MyListModel();
I think it's a closer analogue to React.useState.
useState is for cobbling together state onto what's supposed to be a pure-function. SwiftUI, like MobX (in its normal usage), is class-based and keeps state in a class member.