Data Persistence

Brian Milby brian at milby7.com
Sat Jul 28 00:45:26 CEST 2018


Use case is a major driver though.  If you have no need to hand edit a
file, then LSON is an efficient and easy way to store the data.  It also
has the benefit of being able to easily store binary data if needed.

On Fri, Jul 27, 2018 at 5:40 PM, Richard Gaskin via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Alex Tweedly wrote:
>
> On 27/07/2018 20:17, Richard Gaskin via use-livecode wrote:
>>
>>>
>>> >  Using arrays intigues me, especially if I can just keep it in RAM (It
>>> > is a small amount of data for sure).
>>>
>>> One great thing about LC's built-in support for arrays is that it's
>>> built-in.
>>>
>>> JSON has become used in so many other languages that we've forgotten why
>>> it was invented:  to serialize JavaScript objects as simply and efficiently
>>> as possible using features already built into the JavaScript interpreter.
>>>
>>> LSON is that for us, as much a with-the-grain approach to data handling
>>> in LiveCode as JSON is for JavaScript.
>>>
>> I just wish there was a human-readable, human-editable-in-a-text-editor
>> variant of LSON :-)
>>
>
> True, LSON is even closer to BSON ("Binary JSON") than JSON itself, with
> all the machine-parsing efficiencies inherent in a binary format.
>
> The world wanted a human-readable/writable form of JSON too, so YAML was
> invented. :)
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  Ambassador at FourthWorld.com                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


More information about the use-livecode mailing list