Why not just keep using JSON? I don't see what advantage Elm records offer, as a data format.
Robin's encoder/decoder argument is a separate (but interesting!) topic. Elm ports could be altered to translate between JSON and a structurally-equivalent Elm record. I mean, you'd have to make a pretty good sales pitch first, but I don't think the choice of data format on the JS side prevents this. > On Aug 4, 2016, at 10:40 PM, Jesse Schoch <[email protected]> wrote: > > why not just pick something like Ion and make it first class? > >> On Monday, August 1, 2016 at 12:28:45 PM UTC-7, suttlecommakevin wrote: >> http://elm-lang.org/docs/records >> >> Much in the same spirit as EDN, Datomic, Ion, etc., would it make sense to >> enable non-Elm programs to describe data in Elm Record format? >> The simplicity and readability offer so many advantages. > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
