Looks like a wrapper over core data - was wondering if they made it thread safe.
This is a huge annoyance with CoreData, you can’t pass objects between threads.
SwiftData
41–50 of 109 posts
Re: SwiftData
#42I built myself something similar on top of SQLite and Combine. Now I’m confused, should I abandon it and go with the first hand solution? I would actually prefer that but this requires the new versions of the Apple platforms. Why wouldn’t Apple make these available downstream?
Apple need to ensure as many apps as possible raise their deployment target as soon as possible so that users with old devices are encouraged to upgrade to newer devices.
Re: SwiftData
#43Noob here, how does SwiftData compare to Redux (as a paradigm)?
If you need Redux in SwiftUI, you should check out ComposableArchitecture.
Re: SwiftData
#44When out of beta and generally available, this will be useful! Ideally the iCloud sync will work across the same app built for macOS, iOS, and iPadOS.
I used SQLite a few years ago for a Swift/SwiftUI macOS app, and this looks like what I would have used if it was available. All in all, Apple is going in a good direction with Swift, SwiftUI, SwiftData, etc.
Re: SwiftData
#45I built myself something similar on top of SQLite and Combine. Now I’m confused, should I abandon it and go with the first hand solution? I would actually prefer that but this requires the new versions of the Apple platforms. Why wouldn’t Apple make these available downstream?
Apple need to ensure as many apps as possible raise their deployment target as soon as possible so that users with old devices are encouraged to upgrade to newer devices.
The latest stuff is still compatible with 5 year old iPhones.
80% of iPhones run the latest OS precisely because they are dead serious about long term support for devices.
Re: SwiftData
#46Earlier quoted context omitted.
Apple need to ensure as many apps as possible raise their deployment target as soon as possible so that users with old devices are encouraged to upgrade to newer devices.
The latest stuff is still compatible with 5 year old iPhones. 80% of iPhones run the latest OS precisely because they are dead serious about long term support for devices.
5 years could certainly be improved upon. Those devices cost north of 1k now.
I‘ve been an iOS dev since iOS 4, and have always been put off by this sneaky way of planned obsolescence. Older iOS releases do get security fixes, but only a tiny fraction of the fixes newer versions get. I don’t find this applaudable.
Re: SwiftData
#47Earlier quoted context omitted.
They actually can figure that out, though [0]. I hope this can solve some of it because their deployment model is the dumbest fucking thing. I'm glad they figured out how to backport async/await, it's just impossible to use in a serious library otherwise. [0] https://github.com/apple/swift-evolution/blob/main/proposals...
Over 80% of iPhones are running the latest version. I’ll take that any day as a developer over the Android hellscape of versions that need to be tested for and supported. https://www.macrumors.com/2023/06/01/apple-shares-ios-16-ado...
> Over 80% of iPhones are running the latest version.
If the past is any indicator, the number will be over 90% by the time iOS 17 ships this fall.
Re: SwiftData
#48I built myself something similar on top of SQLite and Combine. Now I’m confused, should I abandon it and go with the first hand solution? I would actually prefer that but this requires the new versions of the Apple platforms. Why wouldn’t Apple make these available downstream?
> Why wouldn’t Apple make these available downstream? Because Apple cannot figure out that their deployment model is hamstringing adoption of their technologies.
Why? This way their new stuff get a year or two of free testing and time to mature before widespread adoption.
Re: SwiftData
#49There’s a number of indie devs who rely on https://github.com/ccgus/fmdb for fast persistence. The rebirth of NetNewsWire came with FMDB at its core (https://inessential.com/2020/05/18/why_netnewswire_is_fast). What’s not clear is if a project starts with, say, SwiftData, and finds it to be a bottleneck, how easy is it to remove unless one goes to great lengths to make a clean API between the 2?
Re: SwiftData
#50I built myself something similar on top of SQLite and Combine. Now I’m confused, should I abandon it and go with the first hand solution? I would actually prefer that but this requires the new versions of the Apple platforms. Why wouldn’t Apple make these available downstream?
> Why wouldn’t Apple make these available downstream?
Because it probably relies on new stuff that's only in the new version of the operating system. Otherwise, you'd have to back port a chunk of your new stuff to the older operating system, creating a lot more work for little gain.
And why do all of that when over 80% of the installed base will be running iOS 17 within 8 months, so what are you really gaining?