swift-collections VS yjs

I think Swift Collections is adding that soon-ish, in 1.1.

Sure, those could work. But I’ve found that OrderedDictionary from the swift-collections package is really helpful in cases like this. With that, your source of truth could be OrderedDictionary. Easy constant time lookup by Section, and order is maintained.

It's a part of Swift's Collection package.

Swift Collections

I think it would be helpful if the data structure you ended up with was an OrderedDictionary, which you can use by importing the swift-collections package via spm. That way you can have an ordered reference to the month (key) and array of records for that month (value). Additionally if you need to access an specific month without knowing it’s index for some reason, it is more efficient.

In that case, use Apple's OrderedSet from swift-collections

if your ‘Dictionary’ has a lot of different keys that can vary every time, a ‘Struct’ might not be the best solution. check out ‘OrderedDictionary’ for a ‘Dictionary’ that maintains the order elements are added. https://github.com/apple/swift-collections/blob/main/Documentation/OrderedDictionary.md

You should use OrderedDictionary in swift-collections for that purpose.

One idea is just to use fewer random bits in peerIDs. Yjs (https://docs.yjs.dev/) gets away with just 32 random bits. If you compromise and use 64 random bits, then even a very popular doc with 1 million lifetime peerIDs will have a < 10^-7 lifetime probability of collision.

I've seen it come up often in collaborative text editors.

Also see: https://github.com/yjs/yjs

You are absolutely right that XML is better for document structures.

My current theory is that Yjs [0] is the new JSON+XML. It gives you both JSON and XML types in one nested structure, all with conflict free merging via incremental updates.

Also, you note the issue with XML and overlapping inline markup. Yjs has an answer for that with its text type, you can apply attributes (for styling or anything else) via arbatary ranges. They can overlap.

Obviously I'm being a little hypabolic suggesting it will replace JSON, the beauty of JSON is is simplicity, but for many systems building on Yjs or similar CRDT based serialisation systems is the future.

https://github.com/yjs/yjs/

Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend

CCP needs to revamp proto anyway, due to recent exploits... practically, nothing really prevents 'em from using some sort of CRDT's to make the state of the sig view eventually consistent (yjs lib, if we're speaking frontendian).

Yjs framework: Because it is a CRDT implementation which provides collaborative editing and offline-first capability.

No problem. The database CRUD features are just helpers as an abstraction on top of yjs: https://docs.yjs.dev/. Eweser adds schemas in the form of typescript types to make using it simpler, more structured, and interoperability easier.