Re:30k lines of SwiftUI in production later
by ezfe on Saturday January 28, 2023 @10:39AM
(#34558422)
1) I use IntelliJ for my day job and find it much slower than Xcode
2) yes
3) I don't really use plugins in IntelliJ either - I do in VSCode but only because it's pretty useless without them
4) Not sure what the problem is with this, but I will say I prefer Package.swift projects for anything that isn't targeting a UI runtime
5) App Store update process just doesn't play well with 8GB applications. Either delete it and re-install from App Store or use something like Xcodes.app
Re:30k lines of SwiftUI in production later
by mrtksn on Saturday January 28, 2023 @10:15AM
(#34558196)
On Apple Silicon it's quite performant, I'm sure there are faster things but I don't have complaints on speed o M1 Air. I had complaints on my Intel based mac though.
The bugs can be annoying but they usually go away after restart and cleaning the junk.
> 5) Why does it take half a day to update through the App Store?
But this one is really annoying. Also for some reason in downloads and installs TWICE.
Re:30k lines of SwiftUI in production later
by Pulcinella on Saturday January 28, 2023 @12:16PM
(#34559379)
It’s way, way faster and easier to just download new versions of Ccode from the developer website. I have no idea why doing it through the AppStore is so slow. If you pull up the console log you can see the AppStore app not actually doing anything for 20-30 minutes (even though it’s displaying the download spinner) before it finally decides it’s time to start downloading.
2) It's extremely buggy, like on a daily basis where something just doesn't work for any apparent reason that is usually either fixed by killing Xcode or removing derived data & then killing Xcode
3) Lack of plugins for even the most primitive of features like autoformatters
4) XML for build configs inside .xcodeproj
5) Why does it take half a day to update through the App Store?
I mean it has some nice features functionality-wise, such as the metal debugging toolkit, but the experience of actually coding in it is abysmal. Like so bad that I've been doing as much of my Swift work in VSCode as possible, which Xcode actually prevented for a while due to a bug in how it handled local Swift packages.