www.delorie.com/archives/browse.cgi | search |
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; | |
bh=3GSpBzUwx0+VkeIRfow2qw0ut5bsvR53QuhlsSpfISY=; | |
b=BL2dc6Csy6BEeCuf5yKIYDqwJgejpGm95ROY+hg6Wbl41APWHQqsS3Ai15gHjmJCEf | |
B0DiwQC6MNh1R/2mz2cvCy43lurp9AZDyacYL+ExA6Gz4XSO+YhrH3HEY0pw+odDY2PC | |
QH7W/VImE0o9Jg2uIbDPp//rC3XhdwAZ8PcRBJ5Nqc7SsHPaQI5ENzSXVmhe6q8p0Ywy | |
xuUeThSeDCE+6uJmccR2eAD/FQSGWHcC/dw2CivfTp8OxflgQ4SEV1e8peqOPq+ktz2R | |
V6TpgnDhW3xbpub8aghXRHfqy/5qyo+3L5cU2as6/KoD9hvvwwclmh0ziPmj/ZHcyqPf | |
hsyQ== | |
MIME-Version: | 1.0 |
X-Received: | by 10.107.6.74 with SMTP id 71mr6869944iog.16.1442002481840; Fri, |
11 Sep 2015 13:14:41 -0700 (PDT) | |
In-Reply-To: | <D3D5A923-FAF9-4665-A0DB-A8D6A8BEA5A3@noqsi.com> |
References: | <alpine DOT DEB DOT 2 DOT 00 DOT 1509111150410 DOT 2482 AT lichen> |
<B94E2C24-8B63-46FC-A551-9E4B14B817C9 AT noqsi DOT com> | |
<201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com> | |
<F24E14C9-8427-4688-A27A-1EBE0F669995 AT noqsi DOT com> | |
<201509111732 DOT t8BHWnF7005271 AT envy DOT delorie DOT com> | |
<960028A6-F16B-4276-B838-E9F0D2959A6F AT noqsi DOT com> | |
<55F32375 DOT 2020505 AT ecosensory DOT com> | |
<FC9C2933-89CE-44FD-A9EE-CA2721405ACE AT noqsi DOT com> | |
<201509111941 DOT t8BJfqWl010427 AT envy DOT delorie DOT com> | |
<D3D5A923-FAF9-4665-A0DB-A8D6A8BEA5A3 AT noqsi DOT com> | |
Date: | Fri, 11 Sep 2015 16:14:41 -0400 |
Message-ID: | <CA+uY=MS5ZOTHXDe9taav+0tCiZOqhtAJU2KO-xyRA3SrQVvLNw@mail.gmail.com> |
Subject: | Re: [geda-user] About reinventing the wheel, and how to avoid it |
From: | "Russell Nelson (russnelson AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
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 |
--001a113deb38b2333d051f7e5d4f Content-Type: text/plain; charset=UTF-8 I believe that what DJ is saying is that you should feel free to do that, but if he changes the API and your software stops working, that's not going to keep him awake at night. On Fri, Sep 11, 2015 at 3:58 PM, John Doty <jpd AT noqsi DOT com> wrote: > > On Sep 11, 2015, at 1:41 PM, DJ Delorie <dj AT delorie DOT com> wrote: > > > > >> You're saying that when the #1 gEDA developer thinks its a good > >> thing to prevent users from using the tools in ways the developers > >> don't approve of that I shouldn't worry? > > > > For the record, I don't think that. > > > > You wrote: > > > I meant, there may be internal > > functions that were never intended to be official (or even public), > > that someone discovered and (ab)used in a workflow. There must be a > > way to let that API change, despite its use, else we'd be unexpectedly > > locked into something we don't want. > > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > > --001a113deb38b2333d051f7e5d4f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I believe that what DJ is saying is that you should feel f= ree to do that, but if he changes the API and your software stops working, = that's not going to keep him awake at night.</div><div class=3D"gmail_e= xtra"><br><div class=3D"gmail_quote">On Fri, Sep 11, 2015 at 3:58 PM, John = Doty <span dir=3D"ltr"><<a href=3D"mailto:jpd AT noqsi DOT com" target=3D"_blan= k">jpd AT noqsi DOT com</a>></span> wrote:<br><blockquote class=3D"gmail_quote"= style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><b= r> On Sep 11, 2015, at 1:41 PM, DJ Delorie <<a href=3D"mailto:dj AT delorie DOT co= m">dj AT delorie DOT com</a>> wrote:<br> <br> ><br> >> You're saying that when the #1 gEDA developer thinks its a goo= d<br> >> thing to prevent users from using the tools in ways the developers= <br> >> don't approve of that I shouldn't worry?<br> ><br> > For the record, I don't think that.<br> ><br> <br> You wrote:<br> <br> > I meant, there may be internal<br> > functions that were never intended to be official (or even public),<br= > > that someone discovered and (ab)used in a workflow.=C2=A0 There must b= e a<br> > way to let that API change, despite its use, else we'd be unexpect= edly<br> > locked into something we don't want.<br> <br> <br> John Doty=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Noqsi Aerospace, = Ltd.<br> <a href=3D"http://www.noqsi.com/" rel=3D"noreferrer" target=3D"_blank">http= ://www.noqsi.com/</a><br> <a href=3D"mailto:jpd AT noqsi DOT com">jpd AT noqsi DOT com</a><br> <br> <br> </blockquote></div><br></div> --001a113deb38b2333d051f7e5d4f--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |