35 ms·
Swift 6 is not the problem. It's backward compatible. The problem is SwiftUI. It's very new, still barely usable on the Mac, but they are adding lots of new fe
by jjcob 2y ago
Swift 6 is not the problem. It's backward compatible.
The problem is SwiftUI. It's very new, still barely usable on the Mac, but they are adding lots of new features every macOS release.
If you want to support older versions of macOS you can't use the nice stuff they just released. Eg. pointerStyle() is a brand new macOS 15 API that is very useful.
- MBCook 2y agoI can’t remember for sure but there may also have been a recent file system API he said he needed. Or a bug that he had to wait for a fix on.
- therockhead 2y agoIt's been a while since I last looked at SwiftUI on mac, Is it really still that bad ?
- jjcob 2y agoIt's not bad, just limited. I think it's getting usable, but just barely so. They are working on it, and making it better every year. I've started using it for small projects and it's pretty neat how fast you can work with it -- but not everything can be done yet. Since they are still adding pretty basic stuff every year, it really hurts if you target older versions. AppKit is so mature that for most people it doesn't matter if you can't use new features introduced in the last 3 years. For SwiftUI it still makes a big difference.
- therockhead 2y agoI wonder why they haven't tried to back port SwiftUI improvements/versions to the older OSs. Seems like this should have been possible.