This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-10
Channels
- # announcements (6)
- # architecture (2)
- # babashka (30)
- # beginners (90)
- # calva (21)
- # cider (22)
- # clj-kondo (27)
- # cljs-dev (7)
- # clojure (132)
- # clojure-europe (51)
- # clojure-nl (12)
- # clojure-norway (3)
- # clojure-spec (3)
- # clojure-uk (5)
- # clojurescript (69)
- # cloverage (9)
- # conjure (5)
- # core-async (54)
- # cursive (14)
- # datomic (34)
- # emacs (7)
- # fulcro (10)
- # graalvm (40)
- # graalvm-mobile (2)
- # gratitude (2)
- # improve-getting-started (1)
- # introduce-yourself (1)
- # jobs-discuss (61)
- # leiningen (5)
- # malli (6)
- # off-topic (59)
- # pathom (11)
- # polylith (38)
- # reagent (3)
- # reitit (3)
- # rewrite-clj (3)
- # shadow-cljs (53)
- # tools-build (35)
- # transit (8)
- # vim (62)
- # web-security (26)
- # xtdb (4)
Is there a plan to support transit+msgpack in the cljs implementation?
there are currently no active plans for anything but I'm hoping we can spend some more intentional time on the transit impls in 2022
the expectation in the past was that js's built-in json support was very fast and thus maybe msgpack was not as valuable in cljs land
(or maybe it didn't exist at the time, don't know)
so I guess my question is why you're asking :)
Curiosity, mostly. Only knew about msgpack from the clj implementation of transit and was reading on https://msgpack.org Their claims about size and serialization speed sounded nice, but in our software we won’t see a volume to really benefit from that, anyways
short time ago I had problems with the fact that JSON.parse
is something internal in transit-cljs
I was dealing with a huge payload, that I was able to represent as Uint8Array
and parse with a specific library uint8array-json-parser
Once JSON.parse
is internal in transit-cljs, the only way to use transit was turning Uint8Array
into a String
, but this operation always failed, because the string would be too big.
I was thinking if in the future, both JSON.parse
and transit-cljs
could use ReadableStream, to allow absurdly big payloads
https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream