@_inside I’ve had issues with using @ Bindable since beta 1 alongside SwiftData, which was making previewing in the canvas near impossible. That said, if you’re content building to simulator/device right now, I have nothing but really amazing things to say about SwiftData. The barrier to entry for data persistence and queries is now so attainable that it’s sure to lead to some amazing improvements for so many apps. Highly recommend powering through any beta issues; it’s so worth it!
@ishabazz@_inside I've been trying and really using SwiftData all summer to have good standing for a fair comparison with Boutique and I swear I'm not trying to be a hater but the implementation does not feel fully baked yet.
@mergesort@ishabazz Yeap, same. Strongly considering Boutique for this project. I'm just getting started so it wouldn't be a big deal to swap out the persistence layer at this point.
@brzz@_inside@ishabazz There are some benchmarks in the Bodega docs because your performance will vary based on what StorageEngine you select. (StorageEngines are plug and play, pick whichever you want, the default is SQLite but you can choose the file system or make your own as some people have done.) The short answer though is fast, not a perfect metric but I haven’t had a single person complain about speed. https://mergesort.github.io/Bodega/documentation/bodega/using-storageengines
@_inside@ishabazz Some of what SwiftData has done has revitalized my interest in making some Boutique upgrades, for example some basic relationships would go a long way. Especially if you don’t have to bring in all of Core Data and Core Data thinking to get them, after the initial “just plug in SwiftData” using it is actually somewhat complicated compared to Boutique. If you do you end up using Boutique you know where to find me (the internet), and I’d love to hear what you think.
@mergesort another thing I was thinking might be nice in Boutique from SwiftData is typesafe predicates so you didn’t have to wait for the DB to return everything and then filter it in Swift. And, of course, @Observable support
@markmalstrom Definitely agree with @Observable but I'm a little less sold on using Predicates as much as I like 'em. (Though open to changing my mind). One of Boutique's principles is that you should never be able to get into a state where the data in memory and data on disk are inconsistent, and given how little memory and Boutique uses to load all the data into memory I'd rather have the guarantee. (Especially now that Boutique's Store has a non-blocking initializer.) https://github.com/mergesort/Boutique/discussions/19
@markmalstrom I’m not saying predicates cause data to go out of sync, but that I believe what Boutique’s in-memory store should always match Boutique’s persistent store. That way there is never a scenario where a write to memory succeeds but the write to disk fails, or vice versa, a similar mindset to the ACID model.
Add comment