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!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: <930E878945B43884.73D527D49882D2C3.525984B971F40DCF@lp.airnews.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3223367723455944@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 44 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Feb 2002 11:55:19 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1014378919 193.71.199.50 (Fri, 22 Feb 2002 12:55:19 MET) NNTP-Posting-Date: Fri, 22 Feb 2002 12:55:19 MET Xref: archiver1.google.com comp.lang.lisp:27110 * "Marc Battyani" | I don't know if you are new to Lisp but I can assure you that the Lisp | community is growing again and more active each day. The only thing that | is needed is more people to contribute all those little libraries instead | of whining that lisp is lacking them. Well... It would be really nice if it were possible to provide a Common Lisp library for a virtual machine in a standard format that got compiled to native machine code either upon execution or importation into the system. In order to offer a Common Lisp library today, you either have to have access to all Common Lisp implementations on all platforms you think your customers might need (and pay licenses for them), or provide source code. I think this choice _really_ sucks. From some of the discussions I have had with others who would like to offer libraries for Common Lisp environments that cost huge amounts of money to use, giving away things for free when there are other operators in the market who make a killing in license fees is unpalatable. I am far from alone in this regard, and this is probably a much bigger "threat" to the market that would sustain Common Lisp than anything else. That the same vendor who charges the heftiest license fees suddenly and without warning kill other commercial projects by offering something as Open Source, often with dubious quality, does not help. Open Source is in my view an overreaction to the evils of Microsoft and it has some "stopping power" towards the progress of those bad people, but I seriously doubt that it has lasting value in its own right. For some cogent thinking on this topic, see this article: A New Paradigm in Intellectual Property Law? The Case Against Open Sources. http://stlr.stanford.edu/STLR/Articles/01_STLR_4/article.htm As for what I would really like to see implemented with all the Common Lisp implementations, I think Java got the virtual machine concept just right. One may argue over the implementation and its many choices and tradeoffs, but specifying the language in terms of this virtual machine is a good thing, not the least because lots and lots of code can be shared without having to share source code, including comments, internal functionality, etc, which one would not like to share as such even though it is necessary support functionality for the shared functionality. /// -- 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.