From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed1.bredband.com!bredband!uio.no!news-feed.ifi.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.scheme,comp.lang.lisp Subject: Re: a cycnical hypothesis/inference Date: 06 Sep 2002 21:53:46 +0000 Organization: Naggum Software, Oslo, Norway Lines: 39 Message-ID: <3240338026339729@naggum.no> References: <8cd70836.0209060453.1588322d@posting.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1031349228 9804 129.240.64.16 (6 Sep 2002 21:53:48 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 6 Sep 2002 21:53:48 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.scheme:14049 comp.lang.lisp:39934 * shinji@swirve.com (Shinji Ikari) | - despite all the passionate argument to the contrary, and contrived | examples aside, they simply don't match the performance of C/C++ for | real world applications [...] I have seen three cases up close and personal where the system was built using Common Lisp and then some idiot manager decided to reimplement it in C++ (and two cases in Java) precisely to get better performance for the application (but not for the programmers), better replaceability of the programmers, and more managability of the whole project, only to discover that it takes about five times as long to reimplement something in C++ as it took to design and implement the first system in Common Lisp, it does not perform noticeably better along any relevant axes, the complexity in C++ makes the programmers just as irreplaceable, and there is no managerial gain to use C++ over Common Lisp, but at this point, they have decided on C++ and work very hard to make it look like a good choice because they would look like utter morons if they could not even pretend that it was a bad choice. The end result is, however, that a project becomes irreplaceable when it has been coded in C++ because it cannot easily be modified and nobody dares start another project to reimplement it until it is much too late and all the old folks who remember the modifiable, adjustable, reprogrammable Lisp system have all quit or been fired. The someone can come in an suggest that it be reimplemented in Common Lisp, again, and save people a lot of money in the process, until the next manager comes along and claims that the cost of the Common Lisp system is too high, they cannot find other Common Lisp programmers, and even though their current resident genius seems happy, they never know when he'll be stolen by another company or quit, or, God forbid, be run over by a bus, so they have to reimplement it, in Java this time, or perhaps C#. | - there are not enough Erik Naggums to go around Yeah, I should get started with the cloning, already. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.