From: Paolo Bonzini <pbonzini@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] RFC: libyajl for JSON
Date: Tue, 3 Nov 2015 14:38:38 +0100 [thread overview]
Message-ID: <5638B8DE.6020709@redhat.com> (raw)
In-Reply-To: <20151103081917.1d348ad1@redhat.com>
On 03/11/2015 14:19, Luiz Capitulino wrote:
> > The value proposition of replacing our flawed JSON parser isn't in
> > saving big on maintenance, it's in not having to find and fix its flaws.
> >
> > If the replacement needs a lot of work to fit our needs, the value
> > proposition becomes negative.
> >
> > A JSON parser shouldn't require much maintenance, as JSON is simple,
> > doesn't change, and parsing has few system dependencies.
>
> Let me suggest this crazy idea: have you guys considered breaking
> compatibility?
Can you explain why that would make sense? :) (Especially since there
is another extension---JSON5---that does exactly what we're doing, so it
probably wasn't that stupid an idea).
Paolo
next prev parent reply other threads:[~2015-11-03 13:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:45 [Qemu-devel] RFC: libyajl for JSON Eric Blake
2015-10-30 20:16 ` Peter Maydell
2015-11-02 8:40 ` Markus Armbruster
2015-11-02 11:49 ` Paolo Bonzini
2015-11-02 12:56 ` Markus Armbruster
2015-11-02 13:47 ` Paolo Bonzini
2015-11-02 14:10 ` Stefan Hajnoczi
2015-11-02 15:46 ` Eric Blake
2015-11-02 19:10 ` Markus Armbruster
2015-11-02 20:08 ` Eric Blake
2015-11-03 7:17 ` Markus Armbruster
2015-11-03 13:19 ` Luiz Capitulino
2015-11-03 13:38 ` Paolo Bonzini [this message]
2015-11-03 13:46 ` Luiz Capitulino
2015-11-03 13:53 ` Paolo Bonzini
2015-11-03 14:26 ` Luiz Capitulino
2015-11-03 14:53 ` Paolo Bonzini
2015-11-03 15:08 ` Markus Armbruster
2015-11-03 13:40 ` Eric Blake
2015-11-03 13:44 ` Daniel P. Berrange
2015-11-03 13:53 ` Luiz Capitulino
2015-11-02 13:17 ` Luiz Capitulino
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5638B8DE.6020709@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.