Article View: comp.lang.functional
Article #1179Re: How to improve the readability of (any) LISP or any highlevel functional language to the level of FORTH ?
From: D Herring
Date: Tue, 04 Jan 2011 05:39
Date: Tue, 04 Jan 2011 05:39
37 lines
3404 bytes
3404 bytes
On 01/03/2011 11:49 PM, rusi wrote: > On Jan 3, 6:05 pm, Tim Harig<user...@ilthio.net> wrote: >> What hurts the LISP community far more is the zealotry of its members, >> their insistance that LISP is the *only* tool for *every* job, and their >> agressiveness in trying to push it off on to everybody else -- whether >> everybody else happens want it or not. Whether this is indicitive >> of the entire community or simply the result of those most apparent, >> I cannot say; but, it leads to the overall impression that the LISP >> community is narrowminded and neophobic. Who would want to be part of >> such a community? Like the dark days of apple, bsd, and linux, there can be some bizarre fanboyism in the lisp community. Geeks are always technical but often not personable. > There are more mundane reasons -- like unsuitability of lisp as a > distribution platform > [See http://www.newartisans.com/about-me.html where John Wiegley > explains why he switched from lisp to C++ for his program ledger ] First he says "It was originally written in C++, but lately I�ve been porting it to Common Lisp, since I�ve realized how much simpler � and more powerful � many of its aspects will become." Then there's a cryptic "I found Common Lisp unsuitable as a distribution platform." Trying not to sound fanboyish, but there are numerous ways to distribute lisp apps. There have been a couple notable improvements in the last year; but several implementations have always offered to spit out an ordinary, standalone executable. I think many readers in the other cross posted newsgroups have seen similar come-and-go users leave their favorite language. - Daniel
Technical Details
Message-ID:
<ifubqn$d1o$1@news.eternal-september.org>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mailReferences:
<80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com> <87pqsgk8v9.fsf@kuiper.lan.informatimago.com> <ca15d8c3-86db-46fd-b35f-1a2596475769@n32g2000pre.googlegroups.com> <mux7hemmgb5.fsf@uzeb.lrde.epita.fr> <ifshjk$hqq$1@speranza.aioe.org> <1fdef538-9257-4ff6-9f5b-c96883349f07@n32g2000pre.googlegroups.com>Show Full Headers
Complete Article Headers
X-Google-Thread: ee3de009bc,1641de092071599d X-Google-Attributes: gidee3de009bc,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,CP1252 Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: D Herring <dherring@at.tentpost.dot.com> Newsgroups: comp.lang.functional,comp.lang.lisp,gnu.emacs.help,comp.lang.forth,comp.lang.prolog Subject: Re: How to improve the readability of (any) LISP or any highlevel functional language to the level of FORTH ? Date: Tue, 04 Jan 2011 00:39:34 -0500 Organization: A noiseless patient Spider Lines: 37 Message-ID: <ifubqn$d1o$1@news.eternal-september.org> References: <80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com> <87pqsgk8v9.fsf@kuiper.lan.informatimago.com> <ca15d8c3-86db-46fd-b35f-1a2596475769@n32g2000pre.googlegroups.com> <mux7hemmgb5.fsf@uzeb.lrde.epita.fr> <ifshjk$hqq$1@speranza.aioe.org> <1fdef538-9257-4ff6-9f5b-c96883349f07@n32g2000pre.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 4 Jan 2011 05:39:35 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="Q7hmocNssIwDEuQbezMefg"; logging-data="13368"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19oq7V/nFDgVUtqGGss5jP1" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Thunderbird/3.1.7 In-Reply-To: <1fdef538-9257-4ff6-9f5b-c96883349f07@n32g2000pre.googlegroups.com> Cancel-Lock: sha1:jUeAgf4u20b6hHpcLPBxcbmwSi8=