How did you find this tutorial? I can't seem to find it by navigating on the developer site.
A friend sent me this Tweet: https://twitter.com/zntfdr/status/1338423623149707265?s=21.
SwiftUI tutorials rewritten completely
61–70 of 115 posts
Re: SwiftUI tutorials rewritten completely
#62Oh wow, I personally know someone who joined the dev pubs team to work on this documentation. I think a big factor in the improvements was their hiring practices. Traditionally Apple has required that employees be on-site. Their dev pubs team is a notable exception and a signify part of that team is remote.
When has Apple traditionally required employees to be on site? I know a few people who have worked remote at Apple for over a decade.
Know a bunch of people working remotely for Apple too
Re: SwiftUI tutorials rewritten completely
#63So far dealing with stuff like PayKit SwiftUI integration still feels really bad. There's just tons of stuff expecting UIKit and it will take a while before all of that stuff is ported. SwiftUI is really great, Combine can be hard to get into for people not initiated in Reactive and generally it's as fast to build stuff in as Flutter without dealing with the tragedy called Dart.
What is wrong about Dart? I come from a Kotlin background and I don't see anything wrong with Dart honestly
Failed to take over the Web as Chrome team was driving it, then ChromiumVM got dropped, several key designers like Gilad Bracha and Lars Bak left the project, it was ultimely rescued by AdWords team, which had just migrated away from GWT into Dart, got rebooted into a strong typed language with type inference, and picked up by the Flutter team.
Nowadays it is basically a language to write Flutter applications, hardly worthwhile to bother using it for anything else.
Flutter is taking place on Google politics, while Google lets Flutter, JetPack Composers and PWAs play the game of cross platform GUI frameworks, with the difference that Kotlin and JavaScript/TypeScript have a much broader eco-system than Dart.
Re: SwiftUI tutorials rewritten completely
#64Man I wish Xcode was a decent IDE
Odd, I don’t really like IDEs but I think Xcode is among the least shitty IDEs out there. Too many IDEs have just terrible GUI design.
Re: SwiftUI tutorials rewritten completely
#65Man I wish Xcode was a decent IDE
Instead of an excellent one you mean?
Re: SwiftUI tutorials rewritten completely
#66Man I wish Xcode was a decent IDE
Me too. I don’t understand how they release an IDE without Vim emulation or some support for plugins that enable Vim emulation. It’s quite miserable. Last time I checked you had to root the app to install a Vim extension.
So weird. I guess it might be because 99.9% of swift developers want as little vim as possible in their lives.
Re: SwiftUI tutorials rewritten completely
#67Man I wish Xcode was a decent IDE
I used Xcode recently and it's gotten a lot better. It's still not as good as IntelliJ or AppCode but it's usable. I remember around when Swift came out, Xcode was so bad that I couldn't even use it because typing was ~1 character/second and it would crash every few minutes. It's definitely recovered from that and I can actually type without lag now.
Sounds like an unusual problem. I cannot remember having that problem and I was using Swift from the beginning.
For me Xcode is quite nice. Didn’t like AppCode. Not sure why people are so enthusiastic about it. What does it give besides better code completion? Development is a lot more than code completion.
Re: SwiftUI tutorials rewritten completely
#68Is SwiftUI just an abstraction over AppKit and UIKit ? Does it bring any widgets of its own - ie something native to SwiftUI as opposed to being wrapped ? (apart from the declarative stuff)
That’s not really the right question to ask. Yes in some cases it is backed by UIKit, for now, but that can change at any time.
It is a completely new paradigm, that’s it. Implementation details are just that.
Re: SwiftUI tutorials rewritten completely
#69Man I wish Xcode was a decent IDE
If there's anything you can credit the Google team for, it's using IntelliJ as the basis of the Android IDE.
I would have preferred them sticking with Eclipse. Sure, the Android plugins for Eclipse were pretty bad, but that was all Googles fault. They could have just fixed their plugins.
Re: SwiftUI tutorials rewritten completely
#70Earlier quoted context omitted.
Because it’s native to the platform. Seriously, that’s huge. The React Native toolchain is cumbersome to say the least. There’s something to say about a first-class library, meaning one that is being used exactly as designed. I mean, why do people use Javascript? Because it’s the native language of the browser.
Yea I don’t disagree, but what development team has the luxury of choosing SwiftUI? Most places hiring are looking for cross platform “2 developers for the price of one” ... and the burden of dealing with cumbersome react native falls on the developer.
In my experience, cross platform development only works for simple apps. If all you’re doing is fill in some forms and update a database, sure, go with a cross-platform toolkit.
If you’re doing anything more complicated than that, the productivity gains diminish quickly to the point where it’s easier and faster to just build to native applications.