X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6ECsJR+eYh6hPaaJiHS6caz/k5nuqbiXanYPxrf1dvM=; b=k3QLPNMGh6yHu2qnyjV+IMdP0eRS+G3FcUP5Fp5rJ8hJjaTOOTxuX9uqEMIsDftYr5 EuQ76BoV0xfRTNZJAzQO7F38LLItvzHFSdYMsIQoaXjrQO2RHvA9jI8Lyvw9JVm1WHSt hk2RD11Lvf7TmNqfIzajNTgRmCMoUixqeJ+Rp9D+3A6vWZjQysmxlta9+xOqMwETvtSu rzfmi+TsSlXCZaFeTF06KDm4jqD9kXBy55cLpbIITyZ/iLgySoCDOokaFaS1y6925+03 JuywgQdqJiuzfXdJDDzCTRF8Yt4JXdKbWJ+AI7zaEo34BCOC3m2+8494o1FkKt0B7OGf S1hA== MIME-Version: 1.0 X-Received: by 10.194.173.233 with SMTP id bn9mr103900991wjc.1.1452036281122; Tue, 05 Jan 2016 15:24:41 -0800 (PST) In-Reply-To: <20160105182120.3237F809D79B@turkos.aspodata.se> References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG> <20151222232230 DOT 12633 DOT qmail AT stuge DOT se> <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <0FCF3774-F93C-4BFF-BB61-636F75DCCACB AT noqsi DOT com> <20160105182120 DOT 3237F809D79B AT turkos DOT aspodata DOT se> Date: Tue, 5 Jan 2016 14:24:40 -0900 Message-ID: Subject: Re: [geda-user] A fileformat library From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=089e0122f088bccb8405289e8a6a Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --089e0122f088bccb8405289e8a6a Content-Type: text/plain; charset=UTF-8 On Tue, Jan 5, 2016 at 9:21 AM, wrote: > Britton Kerin: > > On Sun, Jan 3, 2016 at 6:25 PM, John Doty wrote: > ... > > > Although these are good measures, once you adopt them you may start > asking > > > yourself why you aren't just using a binary format. The argument for > text > > > is that you can glance at a chunk of it and easily tell what's going > on. > > > A stronger argument for text is that you can process it with > text-oriented > > > tools. > > But ultimately the reason for wanting to use those text-oriented tools is > > the same: you can see what you're working on with your own eyes. In > every > > other respect binary is better. > > I counter that. > . you have to check a binary file for valid values just as you do for a > text file > . if your binary file is in some way invalid, you will have a greater > problem correcting it than a text file > . discussing why a file is invalid is easier with a text file > . a binary file might be smaller, but that does not matter much > . text files are better provided for by version systems (e.g. git) > . it is easier to write tools that write text than binary, because > debugging the output is easier > Regarding vcs of text data files for GUI program, it's a stretch to claim that the fact that they're text makes them much more compatible. The diffs are only useful for the most trivial of cases. For it to be really useful you need a (non-text) diff viewer of some sort. All the rest of the above still boil down to examples of things that are easier because you can see the data, and therefore manipulate and validate it more easily. > Also, there is no reason to change a file format unless you change the > functionality it provides, I have to "side heavily" with John on this. > If you want to change the file format, you first have to provide some > goodies that will make people to accept it. And no such "goodie" > thing has appeared. > A little while back a PhD Stefan Salewski put together a very good start on a very nice router. IIRC he said 300-400 hours of effort, probably about $100k worth with overhead in the american market. It's not C (for good reasons) and currently can't talk to pcb at all. I would like to somehow arrange things such than efforts like this could maybe get used. > You might write a library that reads and writes the files and if people > find it useful, they will start using it, else, it will be just your own > project. > True. It might be useless but should at least be non-destructive. Britton --089e0122f088bccb8405289e8a6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Jan 5, 2016 at 9:21 AM, <karl AT aspodata DOT se> wrote= :
Britton Kerin:
> On Sun, Jan 3, 2016 at 6:25 PM, John Doty <jpd AT noqsi DOT com> wrote:
...
> > Although these are good measures, once you adopt= them you may start asking
> > yourself why you aren't just using a binary format.=C2=A0 The= argument for text
> > is that you can glance at a chunk of it and easily tell what'= s going on.
> > A stronger argument for text is that you can process it with text= -oriented
> > tools.
> But ultimately the reason for wanting to use those text-oriented tools= is
> the same: you can see what you're working on with your own eyes.= =C2=A0 In every
> other respect binary is better.

I counter that.
. you have to check a binary file for valid values just as you do for a
=C2=A0 text file
. if your binary file is in some way invalid, you will have a greater
=C2=A0 problem correcting it than a text file
. discussing why a file is invalid is easier with a text file
. a binary file might be smaller, but that does not matter much
. text files are better provided for by version systems (e.g. git)
. it is easier to write tools that write text than binary, because
=C2=A0 debugging the output is easier

Regarding vcs of text data files for GUI program, it's a stre= tch to claim that the fact that they're text makes them much more compa= tible.=C2=A0 The diffs are only useful for the most trivial of cases.=C2=A0= For it to be really useful you need a (non-text) diff viewer of =C2=A0some= sort.

All the rest of the a= bove still boil down to examples of things that are easier because you can = see the data, and therefore manipulate and validate it more easily.
=C2=A0
Also, there is no reason to change a file format unless you change the
functionality it provides, I have to "side heavily" with John on = this.
If you want to change the file format, you first have to provide some
goodies that will make people to accept it. And no such "goodie"<= br> thing has appeared.

A little= while back a PhD Stefan Salewski put together a very good start on a very = nice router.=C2=A0 IIRC he said 300-400 hours of effort, probably about $10= 0k worth with overhead in the american market.=C2=A0 It's not C (for go= od reasons) and currently can't talk to pcb at all.=C2=A0 I would like = to somehow arrange things such than efforts like this could maybe get used.=
=C2=A0
You might write a library that reads and writes the files and if people
find it useful, they will start using it, else, it will be just your own project.

True.=C2=A0 It migh= t be useless but should at least be non-destructive.
=C2=A0
=
Britton

--089e0122f088bccb8405289e8a6a--