transit

mpenet 2022-02-03T12:59:30.406349Z

would be nice to be able to customize serialization per value, ex have some specialized maps serialized as an array of values. I know you can do that with Records for instance but not regular maps

mpenet 2022-02-03T12:59:55.480499Z

Then I guess it's all trade-offs, could be done with extend-with-metadata? true, but at a (performance) price

mpenet 2022-02-03T13:00:11.737089Z

if you have a better way to do this, I am all ears

dnolen 2022-02-03T15:33:48.032449Z

@dnolen has joined the channel

borkdude 2022-02-03T15:36:40.981159Z

Thanks for looking into the metadata-on-symbol issue. Another issue I've worked around for a long time is the slow serialization of big maps. https://github.com/cognitect/transit-clj/issues/43 No hurry, since my current workaround still works, but it seems this issue is related: https://github.com/cognitect/transit-clj/issues/46

Alex Miller (Clojure team) 2022-02-03T15:40:46.318839Z

yeah, I think that's one of the highest priority issues in there. from a broad perspective, consumers have different needs re flushing frequency. I don't know what the answer will be on that but it is definitely something I think we should work on

Oliver George 2022-02-03T19:43:06.995459Z

Quick comment in passing. I think python-transit has compatibility issues with python 3.10. Something to do with the collection module.

Alex Miller (Clojure team) 2022-02-03T20:55:57.830329Z

for any issues like this, it's best to file an issue on the impl repo for tracking

Alex Miller (Clojure team) 2022-02-03T20:56:18.666329Z

https://github.com/cognitect/transit-python/issues for example

Alex Miller (Clojure team) 2022-02-03T20:57:01.859679Z

python unfortunately is one where we've a series of maintainers over the years, none of whom still work at Cognitect