From: HiPhish <hiphish@posteo.de>
To: jbranso@fastmail.com
Cc: guile-user@gnu.org
Subject: Re: A value for "nothing"
Date: Sun, 26 Aug 2018 22:25:05 +0200 [thread overview]
Message-ID: <2870707.xeUVe6UqSq@aleksandar-ixtreme-m5740> (raw)
The main advantage of JSON is that it is human-readable. This is great if you
want to save the data on disc and be able to get it without needing special
software, or if you want to write it out by hand but be able to parse it by a
computer. I actually had done that, I maintained a number of records by hand
and use a small script to splice the data in a modified form into a LaTeX
document.
However, being text-based becomes a liability when there is no need for human
readability. For instance, if you want to send data between processes there
will never be a human who will eyeball it, size and parsing efficiency are
much more important. JSON is non-trivial to parse.
I am writing this implementation of MessagePack because I want to be able to
write a Neovim client for Guile. This will effectively allow writing Neovim
plugins in Guile: Neovim launches an external Guile process and the two
processes communicate via RPC using MessagePack as the protocol. This way
Neovim can be retrofitted with any language for writing plugins; old Vim
needed be be compiled with support for foreign scripting languages baked into
the binary.
next reply other threads:[~2018-08-26 20:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 20:25 HiPhish [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 21:49 A value for "nothing" HiPhish
[not found] ` <CAD2gp_Sg-aDXZKfOcL-i2py7ne4c0Cp+2HvKS4DYi1Antm_B1A@mail.gmail.com>
2018-09-14 22:45 ` HiPhish
2018-09-15 0:26 ` John Cowan
2018-09-15 14:50 ` HiPhish
2018-09-15 18:28 ` Keith Wright
2018-09-15 21:50 ` Edwin Watkeys
2018-09-15 22:16 ` HiPhish
2018-09-15 22:23 ` Edwin Watkeys
2018-09-15 22:13 ` HiPhish
2018-09-15 22:45 ` David Pirotte
2018-08-26 10:13 HiPhish
2018-08-26 17:21 ` Thomas Morley
2018-08-26 17:27 ` Joshua Branson
2018-08-26 17:49 ` John Cowan
2018-08-27 4:52 ` Mark H Weaver
2018-08-27 13:00 ` John Cowan
2018-08-27 21:29 ` Mark H Weaver
2018-08-27 21:32 ` Mark H Weaver
2018-08-26 20:07 ` Mark H Weaver
2018-08-26 22:08 ` Matt Wette
2018-08-27 8:04 ` tomas
2018-08-27 20:12 ` Mark H Weaver
2018-08-27 20:46 ` Mark H Weaver
2018-08-28 0:50 ` Matt Wette
2018-08-28 6:58 ` Mark H Weaver
2018-08-28 15:19 ` John Cowan
2018-08-28 15:38 ` Mark H Weaver
2018-08-28 15:59 ` Mark H Weaver
2018-08-28 16:12 ` John Cowan
2018-08-28 17:15 ` Mark H Weaver
2018-08-28 19:07 ` Mark H Weaver
2018-08-27 20:54 ` Hans Åberg
2018-08-27 0:17 ` Panicz Maciej Godek
2018-08-27 8:02 ` tomas
2018-08-27 8:29 ` Panicz Maciej Godek
2018-08-27 8:29 ` HiPhish
[not found] ` <8840615.kRvQfVdCvZ@aleksandar-ixtreme-m5740>
[not found] ` <CAD2gp_QLqd=_RbF=HTEbCLp1onmUq-c74g0FXTvMgdz8JB4-8A@mail.gmail.com>
2018-08-27 8:24 ` HiPhish
[not found] ` <3467110.H24gZIzStD@aleksandar-ixtreme-m5740>
[not found] ` <87ftz0vidc.fsf@netris.org>
2018-08-27 8:40 ` HiPhish
2018-08-27 12:37 ` Ludovic Courtès
2018-08-27 19:49 ` Mark H Weaver
2018-08-28 7:52 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2870707.xeUVe6UqSq@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=guile-user@gnu.org \
--cc=jbranso@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).