Re: gEDA-user: Functional blocks and PCB format changes

[Armin Faltl <armin.faltl@xxxxxx>]

Kai-Martin Knaak wrote:
> Andrew Poelstra wrote:
>
>   
> > The problem I have with JSON (and to some extent, Lisp) is that it is
> > not self-documenting. You can't open a JSON document and immediately
> > see what everything is and what it does; it just looks like gibberish
> > and brackets.
> >     
>
> +1
> Whatever format is going to be chosen, it should be friendly to human users. 
> In the days of TB hard disks, GB RAM and GHz processor clocks there is no 
> need to compromise readability to save some bits. 
>   
<emote_mode_please_skip_if_offended>
Because of progress in hardware, I can lift terrabytes easily. To all, 
that think
<what_not_pointless_name_which_is_very_verbose>C5<\what_not_pointless_name_which_is_very_verbose>
is friendly to humans, I wish they have to wade through this .... up to 
their nose for ages.
Who needs whitespace? I mean, if the parser can do without it, why waste
some thought on pretty printing. MS don't pay their OSS compatibiltiy 
guys for that.

I've been programming HTML for years - it's ok, but not my favourite choice.
+1 to JSON or YAML ;-) and a very concise choice of names. We don't have 
extremely
complicated structures, so 3 brackets are managable.
<\emote_mode_please_skip_if_offended>

Would this have been comprehensible as:
{
   "emote_mode_please_skip_if_offended":
   "Because of progress in hardware,..."
}
? At least it's machine-convertible to XML. Does XML have a notion of 
orderd lists?


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user