An alternative could be to use protocol buffers <https://developers.google.com/protocol-buffers/> or similar mechanisms. In fact, I have been working on supporting this in elm <https://github.com/tiziano88/elm-protobuf>, although it is not production-ready yet. If anyone is willing to help out, drop me a line (or send me a PR) :)
On Tuesday, 2 August 2016 14:33:10 UTC+1, Robin Heggelund Hansen wrote: > > I assume the main upside would be less need to create json > decoders/encoders? It would work just like sending stuff through a port? > > The only thing that wouldn't serialize well, is functions, which could > just be silently ignored when encoding (this is what JSON.stringify does) > > Also, one wouldn't really need to invent yet another data format. One > could use something like Transit for this (which is a format on top of > JSON, with a couple of cool stuff like caching). > -- 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.
