X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com X-TCPREMOTEIP: 100.0.183.69 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_84674196-CFF1-4623-9216-9DBE595C108B" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [geda-help] Linux Date: Thu, 3 Sep 2020 19:40:29 -0400 References: <20200829221451 DOT GA2565 AT newvzh DOT lokolhoz> <664de6c2-ad96-8298-1b64-ad550acfca64 AT k4gvo DOT com> <20200901193434 DOT GB19839 AT newvzh DOT lokolhoz> <20200902141116 DOT GA2911 AT newvzh DOT lokolhoz> <20200902165424 DOT GB2911 AT newvzh DOT lokolhoz> <333FD0E9-238C-445F-AEE4-850B0EA19A88 AT ece DOT orst DOT edu> <2A687A4D-3219-431E-8866-2D11C2418C81 AT noqsi DOT com> To: "Roger Traylor (traylor AT engr DOT orst DOT edu) [via geda-help AT delorie DOT com]" In-Reply-To: Message-Id: <0839C430-BE38-4A0C-AD1A-0DD9F75A8DDD@noqsi.com> X-Mailer: Apple Mail (2.3273) Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --Apple-Mail=_84674196-CFF1-4623-9216-9DBE595C108B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Sep 3, 2020, at 6:01 PM, Roland Lutz wrote: >=20 > On Wed, 2 Sep 2020, John Doty wrote: >> I favor Lepton [because] it=E2=80=99s agnostic about which layout = program you use: it has no favored layout component. [=E2=80=A6] >> The layout people I work with all have different favorite tools, so >> decoupling schematic entry and layout is very important to me. >=20 > This is absolutely the same for gEDA/gaf. No, gEDA/gaf is joined to PCB. The tail wags the dog. >=20 >> I found [Xorn-based gEDA] incomprehensible. >=20 > Xorn is an internal component; you don't have to understand or even = consciously interact with it in any way. (But even if you did, it's not = more complicated than the Scheme API.) Except if you=E2=80=99re writing back ends, you do. Or maybe you don=E2=80= =99t call the API Xorn, I never could figure out what =E2=80=98Xorn=E2=80=99= meant. It=E2=80=99s a critical problem: the freedom to adapt the tools = to new jobs comes from the ease of writing back ends. But of course if = gEDA exists to serve PCB, that doesn=E2=80=99t matter any more. >=20 >> Guile is much easier to understand. >=20 > You confuse being used to with understanding. I absolutely believe = you that it's easier for you to work with Guile, as it's the thing you = have been working with for a long time. Most people today, though, = would find working with Python easier--or any other modern language, for = that matter. I=E2=80=99ve done things in Python. It wasn=E2=80=99t the problem. The = problem was to figure out the API. Who, except you, has written a back = end using your approach? >=20 > I mean, just show this Scheme code >=20 > = https://github.com/rlutz/geda-gaf/blob/master/gnetlist-legacy/scheme/gnet-= osmond.scm = > and this equivalent Python code >=20 > = https://github.com/rlutz/geda-gaf/blob/master/xorn/src/backend/gnet_osmond= .py >=20 > to any younger tech person and ask them to figure out what's going on. Yet there was quite a collection of back end authors for gEDA in Scheme, = so it was apparently comprehensible to some, anyway. >=20 > Roland John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_84674196-CFF1-4623-9216-9DBE595C108B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
On Sep 3, 2020, at 6:01 PM, Roland Lutz <rlutz AT hedmen DOT org> = wrote:

On Wed, 2 Sep 2020, John Doty wrote:
I favor Lepton [because] it=E2=80=99s agnostic = about which layout program you use: it has no favored layout component. = [=E2=80=A6]
The layout people I work with all have = different favorite tools, so
decoupling schematic entry = and layout is very important to me.

This is absolutely the same for gEDA/gaf.

No, = gEDA/gaf is joined to PCB. The tail wags the dog.


I found = [Xorn-based gEDA] incomprehensible.

Xorn is an internal component; you don't have to understand = or even consciously interact with it in any way.  (But even if you = did, it's not more complicated than the Scheme API.)

Except if = you=E2=80=99re writing back ends, you do. Or maybe you don=E2=80=99t = call the API Xorn, I never could figure out what =E2=80=98Xorn=E2=80=99 = meant. It=E2=80=99s a critical problem: the freedom to adapt the tools = to new jobs comes from the ease of writing back ends. But of course if = gEDA exists to serve PCB, that doesn=E2=80=99t matter any = more.


Guile is much easier to understand.

You confuse being used to with = understanding.  I absolutely believe you that it's easier for you = to work with Guile, as it's the thing you have been working with for a = long time.  Most people today, though, would find working with = Python easier--or any other modern language, for that matter.

I=E2=80=99ve= done things in Python. It wasn=E2=80=99t the problem. The problem was = to figure out the API. Who, except you, has written a back end using = your approach?


and this equivalent Python code

=  https://github.com/rlutz/geda-gaf/blob/master/xorn/src/backend/= gnet_osmond.py

to any younger tech = person and ask them to figure out what's going on.

Yet = there was quite a collection of back end authors for gEDA in Scheme, so = it was apparently comprehensible to some, anyway.


Roland

John Doty    =           Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com




= --Apple-Mail=_84674196-CFF1-4623-9216-9DBE595C108B--