From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: String encoding in json.c
Date: Mon, 25 Dec 2017 18:21:13 +0200 [thread overview]
Message-ID: <83po72ixs6.fsf@gnu.org> (raw)
In-Reply-To: <cc44ba29-4bef-b401-c150-d64ee7b7c817@yandex.ru> (message from Dmitry Gutov on Sun, 24 Dec 2017 22:48:17 +0200)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sun, 24 Dec 2017 22:48:17 +0200
> Cc: emacs-devel@gnu.org
>
> > The main purpose of Emacs is to be an efficient editor, so if we care
> > about the slow-down of code conversions, we should first and foremost
> > speed up reading and writing files. JSON conversion, with all due
> > respect to them, are not the main business for us, and I'm not even
> > sure JSON objects will frequently be as large as files our users visit
> > all the time.
>
> FWIW, a significant use case for json.el is encoding a structure
> containing the whole contents of the current buffer as one of the values
> (several protocols for external code completion tools use this).
OK, but I presume the size of such buffers is rarely more than 1
MByte, say? Files we visit are quite frequently much larger. Which
is why I say that if the speed of en/decoding is crucial, we should
first and foremost work on speeding up file I/O.
next prev parent reply other threads:[~2017-12-25 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 14:26 String encoding in json.c Philipp Stephani
2017-12-23 14:43 ` Eli Zaretskii
2017-12-23 15:31 ` Philipp Stephani
2017-12-23 15:53 ` Eli Zaretskii
2017-12-23 17:27 ` Philipp Stephani
2017-12-23 18:18 ` Eli Zaretskii
2017-12-26 21:42 ` Philipp Stephani
2017-12-27 16:08 ` Eli Zaretskii
2017-12-24 20:48 ` Dmitry Gutov
2017-12-25 16:21 ` Eli Zaretskii [this message]
2017-12-25 20:51 ` Dmitry Gutov
2017-12-26 4:35 ` Eli Zaretskii
2017-12-26 21:50 ` Philipp Stephani
2017-12-27 2:00 ` Dmitry Gutov
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83po72ixs6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).