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; q=dns/txt; c=relaxed/relaxed;
	d=s5tehnika.net; s=default; h=Content-Transfer-Encoding:Content-Type:
	In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:
	Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
	Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
	List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=4K+AkNHWdsPzAJ81OPlckcw627ZxekAfRen5lZ7JC70=; b=rghJaf1xdR1IqM0kdlAFsjRZXs
	tT95xm2QlA6jEDum6dTZOCWzCseTFPMc5gwMnqRqp35rNAQU1EDDLUfg9lgqfo2LVg1FEHHV4vbpk
	HUnJhDztnDbRZPuYjE86TcMlHTJsWrggeq2F6cCs2SgtdyPsVuqB/X08yx/2biyuWqGz9fx0Rdfnd
	F9mdUThugQNLkWM5jed8tpFAxI1z3w7MJUBew2C0bS4v1ZIsj2SIx7hs1btHe1JMGxf1mhfn+39qk
	/pf1RE6cQa5ZZJgNEpJtBvMOmnZWDlGAsWNisxyevswshW9oULMRwCoGGUmaBZJWAw3xEZ1SQQLeV
	+fVMlQ3A==;
Subject: Re: [geda-user] Plans for gEDA/gaf
To: geda-user AT delorie DOT com
References: <20160723065723 DOT GC17595 AT localhost DOT localdomain>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1607231009290 DOT 7286 AT igor2priv>
 <20160723092248 DOT GF17595 AT localhost DOT localdomain>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1607231423480 DOT 2224 AT nimbus>
 <20160724053502 DOT GM17595 AT localhost DOT localdomain>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1607271434200 DOT 1841 AT nimbus>
 <9719FF2C-AC85-4824-89E9-447216E7FA65 AT sbcglobal DOT net>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1607301258260 DOT 1409 AT nimbus>
 <939E39F7-B4DA-4B56-A640-C7E6E4ECF955 AT sbcglobal DOT net>
 <f5b0d73a-6d4f-d0d6-c67e-d4dea979b974 AT ecosensory DOT com>
 <20160802122208 DOT GA12372 AT visitor2 DOT iram DOT es>
 <193dbc32-63cb-2643-b741-d6bfc6a268e2 AT ecosensory DOT com>
 <201608021635 DOT u72GZ2IH018127 AT envy DOT delorie DOT com>
From: "Brane2 (brane2 AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <695013ee-4123-36be-d1ec-d4ad9f664a5d@s5tehnika.net>
Date: Tue, 2 Aug 2016 22:15:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <201608021635.u72GZ2IH018127@envy.delorie.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.studiofaca.com
X-AntiAbuse: Original Domain - delorie.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - s5tehnika.net
X-Get-Message-Sender-Via: server.studiofaca.com: authenticated_id: brane2 AT s5tehnika DOT net
X-Authenticated-Sender: server.studiofaca.com: brane2 AT s5tehnika DOT net
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

My two centiEUR:

1. Re C++ and other language of the future ideas:

Forget it. World is full of poets that could write best poems ever seen, 
if only they have the right words. Or fonts.

Not to mention constant stream of problems wrt to ever changing c++ std 
abi interface.

And all that for what - where is that one great C++ app that just 
couldn't be done in C ?

There are many packages that just had to be Object-whatever and they 
ended up like fat pigs, dependent on bazillion libraries even for 
simplest things, workign slow and being choked even by moderately more 
complex designs.

Two nice things in C++ ( namespaces, templates) come at a price - name 
mangled functions cost link time etc.

And both can be, for most part done where belong. In preprocessor. Where 
they cost nothing.

There is nothing wrong with C, at least for such purposes.



2.Priority points for new gEDA.

a. Stoyp trying to mindlessly copy others. KiCAD came into being after 
gEDA folks screwed up and neglected looong standing wish of a public for 
functional EDA.
That niche is occupied now- there is no point of running there now.

b. I'd go for simple "lean and mean", performance oriented design, at 
least at the start.

c. let the thing grow organically, so to speak. Don't just showel new 
functionalities just to compare to KiCAD. Add them after deliberation, 
only to see if they will survive public review and confirm/change/remove 
it later.


3. libgeda

WRT to libgeda, I don't see the point. There are many functions in gEDA, 
but they are useful only internaly. After all, package for manipulation 
schematics is- schematic.
Only useful thing that I might want to do is export of schematics into 
other, more general formats. BOM list, SVG, PNG, PDF, or perhaps 
netlist. All of those could be done within a module in gEDA, no need for 
special external library. Also, most part of functionality of libgeda 
probably deals with wrking with structures while editing schematics, 
object import/export htat might be useful for external work is just 
small part of that. So, wrt libgeda I'd worry about performance, not 
external useability.

New CAD has to be razor sharp, deadly tool. Compatibility with 
everything from antikythera onwards it totally ridiculous. Optimize the 
thing for currently ubiquous platforms, and if there is an interest in 
other areas, people will make an effort and port it.

Above all, new tool has to feel as part extension of designer's hands. 
All ops must work fluently and instantly, even on bigger designs. 
Constant flicks and jerks at repaints totally screw up one's 
productivity. Good handling of objects and good, fast 2D redraw routines 
are worth more than 100 bells-and-whistles featues that end up as 
nothing more than bulletpoints a "features table" on some website. 
Having good, simple tools for working with tracks will attract more 
crowd than some esoteric autorouter that no one really uses anyway.