<div dir="ltr">I have no opinion either way in this particular use case (but would defer to those who've had more experience above), but I do know that if Rails used JSON to serialise session cookies by default I'd only be running half-day security workshops.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 29, 2014 at 4:52 PM, Rory Sinclair <span dir="ltr"><<a href="mailto:rory@asmallworld.net" target="_blank">rory@asmallworld.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:Helvetica;font-size:13px">Yep, agree totally - JSON is better for all sorts of reasons, including interchange etc.<br></div><div class="">
<div><div><br></div><div>-- </div><div>Rory Sinclair<br></div><div>Head of Technology</div><div>ASMALLWORLD</div><div><br></div></div>
</div><div><div class="h5"><p style="color:#a0a0a8">On Tuesday, 29 April 2014 at 16:49, Gabe da Silveira wrote:</p>
</div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div><div class="h5"><div><div dir="ltr">On Tue, Apr 29, 2014 at 4:36 PM, Graham Ashton <span dir="ltr"><<a href="mailto:graham@effectif.com" target="_blank">graham@effectif.com</a>></span> wrote:<br>
<div><div><blockquote type="cite"><div><div>I agree, but I’d definitely choose JSON. I think it’s less likely to change in an incompatible manner with the passage of time.<br>
</div>
<br>
I’ve been bitten by supposedly standard serialisation formats evolving in ways that break when read by updated code several times over the years (and one of those formats was Yaml, when a syntax change meant I had to use an old version of Ruby when releasing gems for the best part of a year).<br>
</div></blockquote><div><br></div><div>Wise words these. Taking a gander at the YAML spec ought to give any software engineer serious pause. It is an amazingly powerful language, but I would only use it if all the above are true:</div>
<div><br></div><div>* The only code that needs to access it is ruby, YAML is not as well supported and not as powerful with languages other than ruby</div><div>* I really need the rich features of YAML such as being able to serialize ruby objects.</div>
<div>* I am never editing it by hand as there are terrible things that you will never see coming, like, try running this in an irb and weep in horror:<br></div><br><font face="courier new, monospace">YAML.load(" FI: Finland\n NO: Norway\n SE: Sweden")</font><br>
<br></div><div>JSON is well-defined, simple and relatively terse. Use it if you can.</div></div></div>
</div></div></div><div class=""><div><div>_______________________________________________</div><div>Chat mailing list</div><div><a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a></div><div><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a></div>
</div></div></div></span>
</blockquote>
<div>
<br>
</div>
<br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote></div><br></div>