Live data from Hacker News

SwiftUI tutorials rewritten completely

developer.apple.com

51–60 of 115 posts

Re: SwiftUI tutorials rewritten completely

#51
post #46

Earlier quoted context omitted.

If there's anything you can credit the Google team for, it's using IntelliJ as the basis of the Android IDE.

Which is one of the reasons I am happy not having to deal with it every single day. Android Studio requires a gaming rig to run properly, Android developer forums are filled with discussions on how to not use it in pain.

IntelliJ is amazing though.

Re: SwiftUI tutorials rewritten completely

#53
So 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.

Re: SwiftUI tutorials rewritten completely

#54
post #9

Man I wish Xcode was a decent IDE

Curious what your issues are? I personally love Xcode for C++.

A lot of the issues I encounter are mostly related to Swift and SourceKit more than they are Xcode. The language server will start choking after a mildly complex project and highlighting and autocomplete will stop working. Sometimes it won’t recover until you delete derived data. Xcode itself is missing some modern features for navigation and a plug-in system however. I’d also like it if the Xcode team could learn what software patches are rather than releasing an 11gb version for every update.

Re: SwiftUI tutorials rewritten completely

#55
post #9

Man 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.

FWIW you can invoke SourceKit LSP with a vim/nvim plugin now and have a really nice Swift editor inside nvim. It doesn’t work with third-party packages yet though so I mostly use it for one off scripts.

Re: SwiftUI tutorials rewritten completely

#56
post #53

So 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

Re: SwiftUI tutorials rewritten completely

#57
post #53

So 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.

I'm curious what you have against Dart?

Re: SwiftUI tutorials rewritten completely

#58
post #5

Is it my imagination or has Apple been quietly improving and expanding the documentation for SwiftUI over the last few months? It's becoming decent, though there are still dark corners. Apple used to be awesome at documentation. I hope this effort extends to Apple's other frameworks.

It's been expanding ever since the WWDC 2019 release, same with other newer frameworks like Combine, and it mostly goes unnoticed. They should have some way of showing what docs have been updated, currently in the Apple Developer app I think it only highlights new articles.

>They should have some way of showing what docs have been updated

Back when I used wrote iOS crap, I used dash as a quick reference for APIs.That was pretty good at alerting me to documentation changes, since it has to download an update. https://kapeli.com/dash

I only started using it (never did buy it) because I was used to using zeal, a free-software alternative.

https://zealdocs.org/

Re: SwiftUI tutorials rewritten completely

#60
post #36

Oh 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.
Post reply on HN