On Tue, Nov 4, 2014 at 1:02 PM, Yuri Astrakhan <yastrakhan(a)wikimedia.org> wrote:
On Tue, Nov 4, 2014 at 3:45 PM, Brad Jorsch (Anomie)
<bjorsch(a)wikimedia.org>
wrote:
There's a long-standing request for Scribunto
to provide library functions
for JSON encoding and decoding. [Advantages: lots of use case, Disadvantages:
potential for abuse]
I feel that most powerful functions could be abused, and at the end of the
day, there is no such thing as a perfect "idiot-proof" way, simply because
there are a lot of brilliant idiots. So instead of prohibiting a function
that is clearly demanded by many developers, let us implement it and rely
on 1) performance tuning once we see a problem, 2) usage/code reviewing, 3)
documenting recommended usage patterns.
Fully agreed. The nice thing about JSON in particular is that it's a
reasonably simple and constrained format, and thus lends itself well
to optimization if its usage becomes widespread enough to support it.
We have a general issue of coming up with better ways of promoting
efficient coding practices in Lua, but that problem is independent of
whether we add JSON support.
Rob