Replace transit

[lgrapenthin]

transit-clj README states:

NOTE: Transit is intended primarily as a wire protocol for transferring data between applications. If storing Transit data durably, readers and writers are expected to use the same version of Transit and you are responsible for migrating/transforming/re-storing that data when and if the transit format changes.

[gws]

@lgrapenthin Thank you for the report!

I don't have a good excuse for that decision since I was aware of that even back when I first wrote this library. At the time I figured my session data was short-lived and so it wouldn't be a big deal, but that only worked for my use case and there's always going to be a point that a user will need to "cut over" with potential data loss if there are breaking changes to the Transit protocol.

If I were to see about a change to the underlying storage format, I would probably use nippy, do you have other suggestions?

[lgrapenthin]

I'd prefer Fressian because its used in Datomic and I prefer the authors. But I have not used nippy and the proposed speed advantage surely looks promising.