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:content-transfer-encoding; bh=lx/DJAoed8LoEvZX5SXcMAXiOX7t80MNPHbGXpRX2oE=; b=nCkPT7cZ9nFVTstEgLjMbfORGLreKjLIbokQDbcN9AN+j80XF7WZe/kSKmVRhZNe8h 1dr3XsX0ENwLmvuewlNa+f6vLX7q0yiC8O4pXWDGVpB8MqxZq/a8ueMZUcbmLEeyYGrq lqN3xmfULaerNo2y6abB2HMmYWsDB0+2JphH3B3u98lw+1wBH76ZkkNwC7ttJ0IunFwp KQ+LnUmY5gJxUqRzfiWCCkpsxOMeUhcuxGnlu19PyaLCqwr0j1W6RYal4oLM7if0FDyQ 6Uuvq/JD6SPrVXnPvrQ1icroEBdReTvATcCDCpZmifPP3m6MdXF6D0IkPVI3v4rO67+W va0w== MIME-Version: 1.0 X-Received: by 10.112.210.6 with SMTP id mq6mr17693601lbc.83.1440378263583; Sun, 23 Aug 2015 18:04:23 -0700 (PDT) In-Reply-To: References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de> <20150822230549 DOT 3750 DOT qmail AT stuge DOT se> <55D9A5AE DOT 9090604 AT jump-ing DOT de> <55D9BC06 DOT 9060106 AT iae DOT nl> <55D9C34A DOT 2090709 AT jump-ing DOT de> <201508232341 DOT t7NNfl9O012371 AT envy DOT delorie DOT com> Date: Mon, 24 Aug 2015 01:04:23 +0000 Message-ID: Subject: Re: [geda-user] Antifork From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t7O14S9q003231 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, Aug 23, 2015 at 11:54 PM, John Doty wrote: > > On Aug 23, 2015, at 7:41 PM, DJ Delorie wrote: > >> >>>> In other words: gschem urgently needs a button "make a PCB from >>>> this" and also a "simulate this" one. >>> >>> Simulation is as simple as pushing a button? Which simulator? Where >>> are models? Which notion of hierarchy are you using? Which >>> schematics? How are your stimuli generated? How is output displayed? >>> So many options. Putting this into gschem is too complicated. You’d >>> need subsystems for script editing and something like make. Except >>> that excellent tools for those jobs already exist. A toolkit should >>> use them, not reinvent them badly. >> >> John, your failing here is that you refuse to consider the option of a >> toolkit that provides easy-to-use defaults. You assume a toolkit must >> always be used the hard way, and must not provide any convenience >> features. > > “Convenience features” that don’t work make it harder to discover what works. I’ve been struggling with Vivado lately… This is something that seems to eat up everyone's time. Fighting with John. Look I happen to think that to a point he is correct about how the tools architecture should be shaped. That said yes I wish it was a point I did not have to hear about so often. Why must everyone take the bate when these comments are made. This thread has real potential to but instead here we are again fighting about something that could have been ignored until it is mentioned in a meaningful context. > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/