From ... Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!npeer.kpnqwest.net!reader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Where's your Lisp software, Janos Blazi? References: <3b97d110_1@news.newsgroups.com> <87elpjn19q.fsf@nkapi.internal> <9nbb15$51s$0@216.39.145.192> <3208894128011321@naggum.net> <9nbofo$9av$0@216.39.145.192> <3208927079518801@naggum.net> <9ndpjt$nd4$0@216.39.145.192> Mail-Copies-To: never From: Erik Naggum Message-ID: <3208965951547384@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 31 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Sep 2001 19:25:51 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: reader3.kpnqwest.net 999977151 193.90.205.95 (Sat, 08 Sep 2001 21:25:51 MET DST) NNTP-Posting-Date: Sat, 08 Sep 2001 21:25:51 MET DST Xref: archiver1.google.com comp.lang.lisp:15969 * Tim Moore > Maybe there is; after all, I'm not even a teacher. However, from my own > experiences in grad school I think I can assert that it will always be > much less of a hassle to use open source software for exposition and > research purposes than closed source. At a certain point "closed-source" > can not be used widely before it stops becoming closed source. I find this a very strange problem. I have not actually been involved in securing funding for commercial projects myself, but I have worked on several, including some medical projects that had absolutely no problem working with the industry. On the contrary, they had to fight them off and had to set up ethics committees and kinds of things to _avoid_ being associated with industry. * Erik Naggum > How much of a Common Lisp system do you expect to be written in Common > Lisp? * Tim Moore > From my experience, anywhere from "a good part" to "almost all." That is not my experience. The parts that provide services outside of the standard are so much larger than the parts that implement Common Lisp and in order to implement them, you need access to system-specific code, which means you have to use functions that cannot be expressed in Common Lisp. That is, if you recursively search for all called functions or methods and you stop at any function or method defined in the standard, there will be a relatively small number of functions that terminate this search with _all_ standard Common Lisp functions or methods. ///