From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc2.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: How I lost my faith (very long) References: <3223114426294576@naggum.net> <3C741BDC.6F538324@brown.edu> <3C746CF8.B3A02DA7@brown.edu> <3c774da1.21924953@nntp.interaccess.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3223397271096662@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 31 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Fri, 22 Feb 2002 20:07:47 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1014408467 193.71.199.50 (Fri, 22 Feb 2002 21:07:47 MET) NNTP-Posting-Date: Fri, 22 Feb 2002 21:07:47 MET Xref: archiver1.google.com comp.lang.lisp:27192 * Thaddeus L Olczyk | Yes and given that Gregor Kiczales was the principle "architect" ( not | meant in the software development sense ) and invented those things | in Lisp, it indicates that he does not think Lisp to grow much. This does not follow. All we can conclude from his choice of vehicle for his ideas is that he found it the locally optimal choice at the time. There is no reason to maximize any crises, here. Common Lisp is _not_ "popular". This fact is never going to change. What we want to do with Common Lisp is not going to be stuff that can be done with a random selection of people off the streat. However, it _is_ getting increasingly harder to start using Common Lisp in a project -- because the path of least resistance goes through a more specialized tool for the kinds of tasks people are now generally starting new projects. Optimizing for popularity is one way to avoid Common Lisp. Optimizing for extensibility, building systems that can themselves be used to build applications, _without_ the annoying Open Source thing, is Common Lisp's forté. The ability to think "system" is not very common with today's crop of programmers who are mostly building inside somebody else's systems (be they Windows or something like KDE or GNOME, or the whole Java system), and Common Lisp programmers have someone gotten into the mindset that they must fit into other systems, and this is where it is least likely to win in the short term. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.