<div><div>
<div><span>This is for Paul Davis.</span></div><div><span><br>
</span>
<span><br>-- <br><div style="font-size: medium; ">Name: Joseph A. Williams</div><div style="font-size: medium; ">Email: joe@joetify.com</div><div style="font-size: medium; ">Blog: http://www.joeandmotorboat.com/</div><div style="font-size: medium; ">Twitter: http://twitter.com/williamsjoe</div><br></span>
<p style="color: #a0a0a0;">On Thursday, June 30, 2011 at 2:51 PM, Loïc Hoguin wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>On 06/30/2011 11:39 PM, Robert Virding wrote:<br><blockquote type="cite"><div>At the Erlang Factory in London after the EEPs run-through we had a<br>small very informal discussion. As a result of that and after a<br>discussion on erlang-questions I think it is very important that we<br>decide something about eep-18 and JSON. I think we should propose a<br>standard representation and write an OTP module which implements<br>encoding/decoding this. The first version doesn't have to be that<br>fast, mochijson2 which is being used apparently isn't fast, and it can<br>be improved later both with better erlang and NIFs. The important<br>thing is that it is *there* and that it is a good representation,<br>otherwise we might end up with something bad just because that is all<br>there is.<br></div></blockquote><br>jsx is already very good. It implements the EEP and is faster and more<br>convenient to use than mochijson2 IMHO.<br><br>See <a href="https://github.com/talentdeficit/jsx">https://github.com/talentdeficit/jsx</a><br><br>-- <br>Loïc Hoguin<br>Dev:Extend<br>_______________________________________________<br>eeps mailing list<br><a href="mailto:eeps@erlang.org">eeps@erlang.org</a><br><a href="http://erlang.org/mailman/listinfo/eeps">http://erlang.org/mailman/listinfo/eeps</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>
</div>
</div></div>