X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sun, 12 Feb 2017 11:04:32 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: the ecosystem (was: Re: [geda-user] gnetlist chaos) In-Reply-To: <20170212091821.GB450@localhost.localdomain> Message-ID: References: <0D03FED9-A309-4F6C-9863-0EC6DB35176D AT noqsi DOT com> <20170211182330 DOT GO21523 AT foo DOT stuge DOT se> <20170211205800 DOT GB14489 AT localhost DOT localdomain> <20170212091821 DOT GB450 AT localhost DOT localdomain> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 On Sun, 12 Feb 2017, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > cleaner, though stopped due to having no support for this in > mainline pcb Disclaimer: I am honestly not trolling here, just sharing my experience. I am absolutely not trying to say what you should do in your branch or in general. What I say is not even specific to this case, it's really just a generic consideration that I genuinely think could be useful to consider. Facts: We've been working on import/export of random external autorouters, schematics editors, simulatros and tools in pcb-rnd lately. Some of these external tools are small, some are big. Some free, some proprietary. A common pattern tho is that we can build a working first version of such a bridge in a few hours or at most in a few days. They are cheap. Even all of them together seem to be cheap. Personal opinions: I believe the future of gEDA (and generally anything non-KiCad on the free EDA tool scene) is not some centralized effort, not some official big pack, not an official all-in-one distribution. I think the future is building random bridges between random tools, without caring whether a given bridge would be also a bridge to all other similar tools or not. If we have a critical mass of such bridges, a random collection of the tools start to form an useful suite. If we don't, users will switch to KiCad or Altium, etc., because "That Just Works (tm)". What I say is clearly duplication of effort and code - waste of time short term. On the other hand, we either get a suboptimal but working solution in t=tomorrow, or we wait for some magic "everyone uses this common protocol/file format/API/lib/mechanism" and have the first solution to offer in t=infinite. (I strongly believe users won't wait till t=infinite.) I don't say anyone should do anything this or that way. I only say we, at pcb-rnd, do build those bridges. If anyone wants to join this decentralized effort, from schematics side, simulation side, autorouter side, "competing"/"alternative" PCB layout tool side, we welcome them. Regards, Igor2