From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 16:18:48 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6424BBB9 for ; Wed, 30 Jul 2014 16:18:48 +0000 (UTC) Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32709249C for ; Wed, 30 Jul 2014 16:18:47 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id rd3so1790546pab.14 for ; Wed, 30 Jul 2014 09:18:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UZW1OmtGRD2ujzPQVEjBztgLML8ObdvzmK/N+ZPxdIE=; b=E4rEl3Jg9Ek53AnQp4K9EsKnyvnfjwr59Mt/cLgV+5Fm3ARkhJU+BsOt1h4VgrAQTE 7/K+Jk7gaToxSU85N0FgWVkup/wfjA25FJlcZHNryiEeHtQh0bUXInDEGpAfhmMvoI9P LdcO7CIHOeM6rDk9Yy0lsMkrDRjmjsYPwRbnq6AzTN8H40bIYX3EfvXqBNbaW91M6dIB Gw+9+iUE0G9XfAKgN3qsAb6OdcwC7B5QBCKbI8Tu8rEtFjw4EqG+OJUUqiVOHIqEvRCv 3+PmgkH3EWxzWeqbLFQvb4uCbgIroVODIrphWI4mrCZl1edmwkyeE01b/hiyE2nF39UE iiQA== X-Gm-Message-State: ALoCoQm6El46QW9Qt62i2LCe5fh6UjkIzbh6LetwrEr2FQoCt8dZ9UH5Jdlk+N4TBxmV5XymKlxF MIME-Version: 1.0 X-Received: by 10.70.38.4 with SMTP id c4mr6207318pdk.108.1406737120892; Wed, 30 Jul 2014 09:18:40 -0700 (PDT) Received: by 10.70.101.41 with HTTP; Wed, 30 Jul 2014 09:18:40 -0700 (PDT) Received: by 10.70.101.41 with HTTP; Wed, 30 Jul 2014 09:18:40 -0700 (PDT) In-Reply-To: <20140730071500.GF37672@ivaldir.etoilebsd.net> References: <20140728055336.GJ50802@ivaldir.etoilebsd.net> <20140729232338.40AA6580A2@chaos.jnpr.net> <20140730034641.46ABE580A2@chaos.jnpr.net> <20140730071500.GF37672@ivaldir.etoilebsd.net> Date: Wed, 30 Jul 2014 09:18:40 -0700 Message-ID: Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML From: Jos Backus To: Baptiste Daroussin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: arch@freebsd.org, Adrian Chadd , Jordan Hubbard , "Simon J. Gerraty" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2014 16:18:48 -0000 On Jul 30, 2014 12:15 AM, "Baptiste Daroussin" wrote: > > On Tue, Jul 29, 2014 at 09:44:17PM -0700, Jos Backus wrote: > > On Jul 29, 2014 8:46 PM, "Simon J. Gerraty" wrote: > > > > > > > > > On Tue, 29 Jul 2014 16:30:53 -0700, Jos Backus writes: > > > >> You certainly cannot wait for all of it to arrive before you start > > > >> rendering. > > > > > > > >Understood. This is why a serialization output format that supports > > > >streaming data is useful. > > > > > > Indeed; XML works fine for that. > > > > Not to beat a dead horse, but so does YAML, and it's more lightweight/less > > verbose so I personally find it more elegant. But sure, XML would work as > > well. > > > YAML is not more lightweight at all, it is really heavy to parse compared to > XML or JSON. By lightweight I meant syntax verbosity, not computational load (although it seems easy to emit). It's a more flexible format, and that comes with a certain price. The question is whether that flexibility is needed or useful. If JSON can't be used because of its limitations, I would personally prefer the less verbose YAML over XML. Jos. > > regards, > Bapt