{"id":46168,"date":"2024-12-16T14:19:32","date_gmt":"2024-12-16T19:19:32","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=46168"},"modified":"2024-12-16T14:19:32","modified_gmt":"2024-12-16T19:19:32","slug":"forked","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/12\/16\/forked\/","title":{"rendered":"Forked"},"content":{"rendered":"

Drew McCormack<\/a> (Mastodon<\/a>):<\/p>\n

I’m launching a new Swift framework called Forked<\/a> for working with shared data, both on a single device, and across many.<\/p>

[…]<\/p>

The merging that @ForkedModel<\/code> provides is pretty powerful. It does property-wise merging of structs, and if you attach the @Merged<\/code> attribute, you can add your own custom merging logic, or use the advanced algorithms built in (like CRDTs).<\/p>

To give an example, the notes<\/code> property above is a String<\/code>. With @Merged<\/code> applied, it gets a hidden power — it can resolve conflicts in a more natural way. Rather than discarding one set of changes, or merging to give somewhat arbitrary results, it produces a result a person would likely expect. For example, if we begin with the text “pretty cool”, and change the text to “Pretty Cool” on one device, and to “pretty cool!!!” on another, the merged result result will be “Pretty Cool!!!”. Nuff said.<\/p>

And this works within your app’s process, between processes (eg<\/em> with sharing extensions), and even between devices via iCloud.<\/p><\/blockquote>\n\n

See also:<\/p>\n