5 ms·
Also worth looking are EDN [0] (mentioned briefly under S-Expressions), Transit [1] and Fressian [2][3]. [0] https://github.com/edn-format/edn https://github.c
by hcarvalhoalves 6y ago
Also worth looking are EDN [0] (mentioned briefly under S-Expressions), Transit [1] and Fressian [2][3].
[0] https://github.com/edn-format/edn https://github.com/edn-format/edn
[1] https://github.com/cognitect/transit-format https://github.com/cognitect/transit-format
[2] https://github.com/Datomic/fressian/wiki https://github.com/Datomic/fressian/wiki
[3] https://www.youtube.com/watch?v=JArZqMqsaB0&ab_channel=ClojureTV https://www.youtube.com/watch?v=JArZqMqsaB0&ab_channel=Cloju...
- peatmoss 6y agoYeah, the author didn’t specify why he thought EDN wasn’t more than “a good start.” I’m curious what it’s missing!
- erikerikson 6y agoIf you follow the link, you'll see that there are no examples of data in the format and the README declares things like that it will provide a BNF when the specification ready. The context seems to imply that it is in an early implementation stage and not ready for non-enthusiast consumption. Also, last updated in 2014.
- jandrese 6y agoWhat's missing is major projects using it I think. Note how for every example he lists the big players keeping it alive.
- bjconlan 6y agoFrom recollection it’s the native data transmission format for Datomic (which is driven by Cognitect/Nubank). I think there is a little bit more to the bias’ of EDN (mostly driven by language preferences in this case).
- hcarvalhoalves 6y agoEDN has a few limitations regarding encoding custom types (tagged literals), and also performance in general. I understand both Transit and Fressian are possible evolutions addressing these points.
- auganov 6y agoI would love edn if it was viable as a standalone format. In practice, programming in clojure it's plain JSON vs transit vs fressian. I tend to go with just JSON.