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=googlemail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=oAEQPzpw2jbFUVq0/d1asGCSb/3fleAJsHzokJRFghU=;
	b=x55ILWqVn3htUUxgBdqGGjE+ojpoNxMEnbRB6LFtbRYgphMnKwGeRGLnahL7JTBqgc
	BgFPCqTBZyzFsJEmz74djxVzN3hCHhi804HnaAHK1pmBJVMU7WfCrTMIKeZjOZvUrXR/
	rMdZ8JjenKV7LdPcmNGxBMQbPeVH4iOyZ07sIMya9b0sU4Tr85lcpkHCRWc9LttA2emH
	78cdGMOzQflubV1i71UiRjm7D8rwLRJf9xpjevM/t2FyXeiu1olB3rC4+yuRwPb4nCP8
	5rNB3AZsn0yW31y7R+n+WxzxkeuHe3r0YPRDdRaN3/tDz/CovqM8Cbwh0HfGCNZY/miY
	Gy6Q==
MIME-Version:	1.0
X-Received:	by 10.60.81.202 with SMTP id c10mr12096644oey.61.1450804235102;
	Tue, 22 Dec 2015 09:10:35 -0800 (PST)
In-Reply-To:	<B7FF4997-34E5-4E61-AD74-28BE54E45801@noqsi.com>
References:	<CAJXU7q9ToaWE+wVJcF76yqHhjYZc5j95VL64cXPey-x4s_j9OA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512221634081 DOT 9035 AT igor2priv>
	<CAJXU7q_oFvUsdQ4zB+9Kp31dhOQPZa7b21AMZ9g_=VpYN1gAnw AT mail DOT gmail DOT com>
	<B7FF4997-34E5-4E61-AD74-28BE54E45801 AT noqsi DOT com>
Date:	Tue, 22 Dec 2015 17:10:35 +0000
Message-ID:	<CAJXU7q9SO+beJYXCdP4iubBnXu7WP1TrqcbJwvRtYz-2YgFQvw@mail.gmail.com>
Subject:	Re: [geda-user] Cross project collaboration on data models
From:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	gEDA User Mailing List <geda-user AT delorie DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id tBMHAcKT013172
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

> I’m doing more with gEDA than ever before. I see no serious bit rot problems. Stability is a good thing. I don’t buy the idea that you need developers to fix what isn’t broken.

It will come... We have often encountered problems keeping up with
porting to new GUILE versions, and it won't be forever away before
GTK2.0 is less common pre-installed on distros.

Nothing insurmountable here - as long as someone remembers enough
about the internals to fix it when it breaks. Its easier if we don't
let obsolescence sneak up on us though - otherwise you'll soon find it
is 2025  , and you have needed to keep that 2014-2015 Linux distro on
a similar era PC, just to run gEDA.

When I first started working on gEDA, that it crashed with _annoying_
regularity... we fixed LOADS of bugs there, and a lot of it was due to
latent bugs exposed by changes in the glib memory manager. gEDA was
always wrong, but it took external changes to convert "wrong but
works", into "crashes and eats your work every 5 minutes". Do you
recall those days?

I have a dim memory of one particularly cruel crash, where it was
triggered by the auto-save code backing up your work (I may also have
just made that up!).


FWIW, one of the reasons I've not been hacking on gEDA and PCB so much
recently is that is mostly does what I need, when I need it - so I do
take your point about the suite being mature.


As for KiCAD...

I wish it well, but I _don't_ enjoy using it. gEDA is a far better fit for me.

I think you often confuse my thoughts on better "integration" or
better "interoperability" with producing an all-in-one closed
tool-chain like KiCAD. Nope.. yuck, yucky. (And IMO, we ought to rip
out all the flattened net-list, PCB like work-flow specific hacks out
of gnetlist).


> This is good, too. As I’ve said before, the hard part about interop is that KiCAD seems to be a sealed world: I can’t find docs on internals.

If you want, I can ask them to point you at them - I'm sure they
exist, just wouldn't know where, since I'm not active in that
community.


Peter

- Raw text -