X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=489tq5OwrGRY8cXCT+x4CXtwY20DT7pL05F8HrgMKak=; b=Jr9mYJLngpItjb2IWdUpigoM6lG+m0knyo6SfQc+Y3dD8R9A2RD3qejY3uPK9XP9Wn pxEqDSNnGoSUdCP8w9G0wy0rtcZcAd6nVKaHY++AIPWDfkXhBltOi3ZfoEkNRFXp/pmj MRmgkyVpgnnI3CWG2OHW+gnu8ogBHQa4iooHGYe0aAC4LIY1eU7cSxIIa6x3hVTRC4xv H5QLAFSNs9PVxbx8/Ne89rbtI712IaALOuO1dPhnDHF0r1vcGTMXQn+P4BdXrJH2zBj0 Bl02N46g5KuSEjdBwGq/CinDzjuS+eNlvps0GdftDMDj3mE4b6phHKDCCMVta8Od1KYs 6Brg== MIME-Version: 1.0 In-Reply-To: <50AB223C.3020207@neurotica.com> References: <50A688B8 DOT 4090809 AT neurotica DOT com> <50A6A95C DOT 5030903 AT neurotica DOT com> <355DEF4F-51BB-44A8-A5F4-D8564E7E7885 AT noqsi DOT com> <20121116213601 DOT 13718 DOT qmail AT stuge DOT se> <66889AAB-3A82-4861-ACB0-B35A876EF6F4 AT noqsi DOT com> <50A83AAA DOT 6060500 AT jump-ing DOT de> <50A8615E DOT 2080800 AT neurotica DOT com> <05730E0F-4DA1-47C8-80BB-5D4F37EFD94E AT noqsi DOT com> <50A8675D DOT 30509 AT neurotica DOT com> <50A95721 DOT 7080704 AT neurotica DOT com> <50AB223C DOT 3020207 AT neurotica DOT com> Date: Tue, 20 Nov 2012 08:33:40 +0100 Message-ID: Subject: Re: [geda-user] Thoughts on gschem UI From: Svenn Are Bjerkem To: geda-user AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 20 November 2012 07:25, Dave McGuire wrote: > On 11/19/2012 09:18 PM, Britton Kerin wrote: >>> If gEDA moves to Perl as its scripting language, I'm going back to >>> pencil and paper. >> >> Perl vs Lisp >> >> one working implementation ~4 different half finished ones >> weird syntax weird undocumented metaprogramming >> nice module repository no repository, just use google :) >> embeddable depends which one you use >> extensible (call C) I have no idea >> one monolithic community ~4 tiny communities >> works fine in vi emacs MUCH more painful to extend IME >> >> Language snobbery aside, lisp really doesn't have much going for it. > > And the PerlTribesmen descend with fire and sword. So predictable. > > I won't even dignify it. > >>> Lisp is used by the ones with long history, but it CONTINUES to be >>> used there because it's a very good tool for the job. Autodesk isn't >>> dumping Autolisp for Perl or Ruby. ;) >> >> Its all just momentum. Nobody is putting it in anything new today. > > Of course. And that's obviously also why the Linux kernel hasn't been > rewritten in Perl. (as has been suggested by other PerlTribesmen) Language wars have never lead to anything, except Richard Stallman calling John Ousterhout a 'parasite' in front of Tim O'Reilly at a conference. I find this a quite amusing history. Somewhere down the road, the decision was taken to use guile as scripting and extension language for gEDA, and not Tcl, even if Tcl at that time was mature. Tcl as an extension language was mature and stable before gEDA went public. Perl was also mature at that time, but except for one waveform viewer I once tried out, I have not seen much perl in the extension league. Maybe the BSD license of Tcl scared the devs that time, or maybe they were pure GNUists. They still live to tell, if they care. I have nothing against guile anymore. At the beginning of gEDA, guile was often a source of problems when it came to stability and compilability, but I guess that is not a problem anymore. Lisp is a nice syntax which helps the programmer indenting his code. Cadence chose to modify their Lisp dialect to accept INFIX notation to make it easier for novice programmer to grasp things, and to write a tad bit less code on the tool command line to get info in and out. Tcl was written for this kind of job, but nobody likes it because they think they must write complete programs with Tcl. I have tried to write applications in Tcl/Tk, and I accept that it is not its primary goal. It is an extension language with an extension language syntax. Python was not written for this kind of job, so everybody loves it because they can write complete programs with it. The object oriented nature of Python is designed to hide details from the user, even at the method implementation level. Hiding details from the user is not the target of EDA automation. -- Svenn