From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!hub1.nntpserver.com!newsfeed01.sul.t-online.de!newsfeed00.sul.t-online.de!t-online.de!fr.usenet-edu.net!usenet-edu.net!freenix!fr.clara.net!heighliner.fr.clara.net!hamster.europeonline.net!newsfeed.europeonline.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: The true faith References: <3219086537399318@naggum.net> <%njZ7.279$iR.150960@news3.calgary.shaw.ca> <3c36fbc5_10@news.newsgroups.com> <4idg3u40ermnp682n6igc5gudp7hajkea9@4ax.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3220084172749450@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jan 2002 11:49:34 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1011095374 193.71.66.49 (Tue, 15 Jan 2002 12:49:34 MET) NNTP-Posting-Date: Tue, 15 Jan 2002 12:49:34 MET Xref: archiver1.google.com comp.lang.lisp:24337 * Raffael Cavallaro | In a sense, the bias that performance is a secondary consideration | flows from a contempt for the brute force method, and a preference for | the algorithmically elegant solution. However, some interesting things | are really only doable because of what can only be described as raw | machine power. If one's more elegant language cannot keep up, then | it's elegance is of little use in this type of cutting edge project. While this is obviously true, the very existence and proliferation of exceedingly slow languages like Perl, Python, and Java, means that people are beginning to understand that performance does not matter for _every_ task and are more than willing to do the logic in a more convenient language. I think Common Lisp may have tried to compete on performance when it should have competed on convenience. On the other hand, I would so love to have all of Common Lisp available to me in a form that would compile to "C-compatible" code, that followed the calling conventions of more widely used languages upon request, so that Common Lisp could be used without having to let it be the master of the whole application. /// --