3 ms·
It's too bad the EDN standard ain't an actual standard or proper spec. I had to rail on those people for fucking ages to get any ambiguities fixed and last I ga
by coolsunglasses 12y ago
It's too bad the EDN standard ain't an actual standard or proper spec. I had to rail on those people for fucking ages to get any ambiguities fixed and last I gave a damn it still:
1. Wasn't congruent with what Clojure's parser allows
2. Defined by whatever Hickey feels this year
I've worked on more than one edn parser in non-Clojure languages, it was Total Hell.
Hitching your wagon to EDN isn't advisable, there are better formats if you need them.
- dj-wonk 12y agoOk, I haven't felt these pains, but I'd like to learn more. * Have you documented the ambiguities? * Have you open-sourced your non-Clojure EDN parser(s)?
- dj-wonk 12y agoWhat are your use cases, and what formats did you prefer?
- dj-wonk 12y agoI don't think that "Whatever Rich Hickey feels this year" is a serious pain point. Rich isn't fickle with changes; quite the opposite. Clojure has evolved, but Rich explains himself well. What changes have bothered you?