X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: multipart/signed; boundary="Apple-Mail=_F04245B1-23CB-426F-A262-DE443A3A0C45"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] A fileformat library X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: <201512240626.tBO6QuW0031998@envy.delorie.com> Date: Thu, 24 Dec 2015 07:46:55 -0700 Message-Id: References: <20151222232230 DOT 12633 DOT qmail AT stuge DOT se> <0F6F1D0F-4F07-48EA-90FE-836EAD4E2354 AT noqsi DOT com> <20151223194905 DOT 7676 DOT qmail AT stuge DOT se> <0AB5D926-731F-4A49-AA26-D06DAE7C2CB0 AT noqsi DOT com> <201512240626 DOT tBO6QuW0031998 AT envy DOT delorie DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_F04245B1-23CB-426F-A262-DE443A3A0C45 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 23, 2015, at 11:26 PM, DJ Delorie wrote: >=20 >> I think that having a file format that enables simple means to >> achieve simple (but specialized) ends is essential to a good >> toolkit. >=20 > Any SQL implementation refutes that. Nobody touches the SQL data file > itself, they all go through a SQL interpreter that accesses the data > on their behalf. Specialized ends are implemented on top of this > interpreter. Except that the user needs to be comfortable with SQL. With our .sch = format, users choose whatever language they are comfortable with from a = long list: AWK, Python, Perl, =85 >=20 > Granted, this means we'd need a well-defined way to do pretty much > anything through whatever means we provide, but saying "access to the > file is required" is just plain wrong. "Access to the data" is a more > appropriate requirement, but making the data file tweakable is a weak > solution to that - no controls, no validation, etc. I want to liberate users, not control them. We have validation tools. = The fact that it is sometimes necessary and correct to ignore their = complaints demonstrates that the capabilities of the geda-gaf toolkit = extend outside the bounds they define. I hope this will always be the = case: geda-gaf=92s limitations will be in the minds of its users rather = than in the minds of its developers. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_F04245B1-23CB-426F-A262-DE443A3A0C45 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWfAVgAAoJEF1Aj/0UKykRvlkP/0Avj8vKecYpHs/Y/Sg9df4I k469HpjdPWH8TZdkKxFWx2sKz/TV1bGAcB0m1W0dJUUZ6/oOXlwwHq/kKak7EsCH 2lNBFTDh6YwMoJIlR9+ui5qwLg0V1Hf02Z6BBueWWpfh3LQ4eIxx0ysuSt1I3N3A kCmgN3rQG6hGNxjXadQavOhEzkpdVFKcywN0FCXcN8JjRDLmuYfUdM0eUJWolng7 zEF/gxMuJt23AZLChIzf9jkkcIk3CW7GWM7pVAqFhI+hPz0eJwMYgpQ/STGu0cPL +aA8SMcne3wxyJ570SLjnIV66rCzmdxf9hagBVDNb2hwAEa0W3HF43wxQM2ca+VQ MWKBuhY+yq/4tL9SyijdIctrDbaTfnwLzzi5yRETH6C/jWL8d2D9iXWA9E7XStU9 33yqHXmgkglIp+9wlBYJdoiF4Sf1Bu8Ex285sMVuwrRdtg2zE32eWJoJPcMiVDur WnHctmKEU9nMygp863np/atsq4XN1HN+jyRDef67fN7qzpUK7mCf7K0TaiH3nbyS MEIN1M5IJOqxqSr5gmGP5N3hv7UJjhgwO/Xr1XVEFXbUiA5ZEYTrLLfDL/tFi3ED vNkNRSg06/+zsro+w8v/Vq/f13huFL3/FX+nfZWEZgAoCCiEUJCxyE26ak/00E4Q jZYRs5ZmYxoYBiUXJOvD =Qtpq -----END PGP SIGNATURE----- --Apple-Mail=_F04245B1-23CB-426F-A262-DE443A3A0C45--