This article is posted at the request of C.W. Yang who
asked me to detail my opinion of Lisp, and for the benefit
of people like him, who may find themselves intrigued by
this language.
The opinions expressed herein are my personal ones, coming
from several years of experience with Lisp. I did plenty of
AI programming back in the day, which is what would now be
called "search" instead.
Due to time constraints, I will refrain from posting any
follow-ups here. Participants of other newsgroups are well
aware of comp.lang.lispe rs' tendency to engage in personal
attacks, so a productive discussion with them is unlikely
anyway.
Permission is granted to copy and distribute this document
without restrictions.
=============== =============== =============== ============
Why Lisp is not my favorite programming language.
=============== =============== =============== ============
(In the following, "Lisp" refers to ANSI Common Lisp)
This article is a collection of facts anyone interested in
Lisp should know about.
---------------------------------------------------------
FACT 1: The fastest Lisp implementations are slow
(See any third-party benchmark: The Great Computer Language
Shootout comes to mind, but the Coyote Culch test is in my
optinion even better: it is a professional-quality
interlanguage benchmark)
As a rule of thumb, the most hand-optimized Lisp programs
will be longer than their C/C++ equivalents, and will run
2-20 times slower using the best compilers.
This alone is half the truth. To get such performance out
of Lisp, one has to add type declarations and shed all
safety checks, which is analogous to casting /everything/
to (void*) in C. This is needed to turn off type tag checks
at run time.
Sadly, Lisp code that was posted to USENET by Pascal
Bourguignon for the Coyote Gulch test did not measure up
even to these low expectations and was 31.6 times slower
than C++, using CMUCL 18d as a Lisp compiler and Intel C++
7.1 (with -O3 -xW optimization switches) as a C++ compiler
on Pentium IV.
---------------------------------------------------------
FACT 2: No one but a small clique of fanatics likes it
No matter how odd or perverted the cause, there will be
followers. In fact, the odder the cause, the fewer, but
more fervent its followers are. Look at any religious cult,
like Scientology, or take a peek in comp.lang.lisp and
listen to Lisp zealots talk about 'making sacrifices for
the cause' (in all seriousness!). Look up "a public
apology" thread started by Pascal Costanza as an excellent
example.
ZEALOTS STOP AT NOTHING TO ADVANCE THEIR CAUSE, AND
PERSONALLY ATTACKING ANYONE WITH A DISSENTING OPTINION IS
THE FIRST THING IN THEIR ARSENAL.
---------------------------------------------------------
FACT 3: The vast majority of people who study Lisp in
school, never want to use it again.
You should already know this if you studied or taught CS
where Lisp courses were offered. Even those students who
are fond of Scheme are usually disgusted by Lisp.
---------------------------------------------------------
FACT 4: Lisp is the most complicated language in the world
It has the biggest standard specification document, which
is also the most obfuscated one - something a lawyer
pretending to be a programmer could have written. C, C++
and Fortran 95 specs are much better written, by people who
can communicate directly and eloquently.
---------------------------------------------------------
FACT 5: Despite its size, Lisp does not define threads or
GUI.
Large libraries are very useful when programming, however
Lisp's many functions and macros hardly qualify.
---------------------------------------------------------
FACT 6: There is no open-source cross-platform native-code
compiler
It was suggested that GCL (GNU Common Lisp) is the only
exception. However, it needs to be noted, that despite its
name, GCL is a dialect of its own, is quite slow even by
Lisp standards, and most alarmingly, unlike with other
compilers, its license requires your, programmer, code to
be GPL if you distribute it with GCL. (Because you will
need to use GCL both as a compiler and a run time library)
---------------------------------------------------------
FACT 7: There is no standard C interface.
C has become a lingua franca for interlanguage APIs. It may
be unfair, but not having a standard C interface is a
serious problem for any language.
EPILOGUE:
I do not hate Lisp, and I think it was a fine tool decades
ago, and I am not going to say "Lisp sucks". However, now
that we have superior languages for coding close to the
iron, high-performance computing, number crunching,
algorithms, scripting and gluing components together, Lisp
should be finally retired. 32 2017
nobody wrote: EPILOGUE:
I do not hate Lisp, and I think it was a fine tool decades ago, and I am not going to say "Lisp sucks". However, now that we have superior languages for coding close to the iron, high-performance computing, number crunching, algorithms, scripting and gluing components together, Lisp should be finally retired.
somebody answers:
Lisp has been declared dead for the past N years. Unlike Algol, Simula 67, PL/I,
Pascal, ... and many more languages that came and went, it is still alife and
kicking. It will be alive and fun to program in for many years to come, because
it still has many advantages over C#, Java, Perl, Python, Ruby, and many other
languages that *will* come and go before Lisp is truly retired.
Long live Scheme
And now it's time to go back and strengthen Scheme even more.
-- Matthias Felleisen, PLT
In comp.lang.c nobody <no************ ****@yahoo.com> wrote:
^^^^^^^^^^^ This article is posted at the request of C.W. Yang who asked me to detail my opinion of Lisp, and for the benefit of people like him, who may find themselves intrigued by this language.
Wow, isn't that nice of you to post for Mr. Yang. I'm sure I, like
everyone on comp.lang.c, is utterly fascinated by Lisp and Mr. Yang's
critique of it. Likewise, I'm sure, for the happy inhabitants of
comp.lang.c++, comp.lang.java. programmer, and comp.lang.pytho n.
Followups set, anonymous crossposting troll.
The opinions expressed herein are my personal ones, coming from several years of experience with Lisp. I did plenty of AI programming back in the day, which is what would now be called "search" instead.
Due to time constraints, I will refrain from posting any follow-ups here. Participants of other newsgroups are well aware of comp.lang.lispe rs' tendency to engage in personal attacks, so a productive discussion with them is unlikely anyway.
Permission is granted to copy and distribute this document without restrictions.
=============== =============== =============== ============ Why Lisp is not my favorite programming language. =============== =============== =============== ============ (In the following, "Lisp" refers to ANSI Common Lisp)
This article is a collection of facts anyone interested in Lisp should know about.
---------------------------------------------------------
FACT 1: The fastest Lisp implementations are slow
(See any third-party benchmark: The Great Computer Language Shootout comes to mind, but the Coyote Culch test is in my optinion even better: it is a professional-quality interlanguage benchmark)
As a rule of thumb, the most hand-optimized Lisp programs will be longer than their C/C++ equivalents, and will run 2-20 times slower using the best compilers.
This alone is half the truth. To get such performance out of Lisp, one has to add type declarations and shed all safety checks, which is analogous to casting /everything/ to (void*) in C. This is needed to turn off type tag checks at run time.
Sadly, Lisp code that was posted to USENET by Pascal Bourguignon for the Coyote Gulch test did not measure up even to these low expectations and was 31.6 times slower than C++, using CMUCL 18d as a Lisp compiler and Intel C++ 7.1 (with -O3 -xW optimization switches) as a C++ compiler on Pentium IV.
---------------------------------------------------------
FACT 2: No one but a small clique of fanatics likes it
No matter how odd or perverted the cause, there will be followers. In fact, the odder the cause, the fewer, but more fervent its followers are. Look at any religious cult, like Scientology, or take a peek in comp.lang.lisp and listen to Lisp zealots talk about 'making sacrifices for the cause' (in all seriousness!). Look up "a public apology" thread started by Pascal Costanza as an excellent example.
ZEALOTS STOP AT NOTHING TO ADVANCE THEIR CAUSE, AND PERSONALLY ATTACKING ANYONE WITH A DISSENTING OPTINION IS THE FIRST THING IN THEIR ARSENAL.
---------------------------------------------------------
FACT 3: The vast majority of people who study Lisp in school, never want to use it again.
You should already know this if you studied or taught CS where Lisp courses were offered. Even those students who are fond of Scheme are usually disgusted by Lisp.
---------------------------------------------------------
FACT 4: Lisp is the most complicated language in the world
It has the biggest standard specification document, which is also the most obfuscated one - something a lawyer pretending to be a programmer could have written. C, C++ and Fortran 95 specs are much better written, by people who can communicate directly and eloquently.
---------------------------------------------------------
FACT 5: Despite its size, Lisp does not define threads or GUI.
Large libraries are very useful when programming, however Lisp's many functions and macros hardly qualify.
---------------------------------------------------------
FACT 6: There is no open-source cross-platform native-code compiler
It was suggested that GCL (GNU Common Lisp) is the only exception. However, it needs to be noted, that despite its name, GCL is a dialect of its own, is quite slow even by Lisp standards, and most alarmingly, unlike with other compilers, its license requires your, programmer, code to be GPL if you distribute it with GCL. (Because you will need to use GCL both as a compiler and a run time library)
---------------------------------------------------------
FACT 7: There is no standard C interface.
C has become a lingua franca for interlanguage APIs. It may be unfair, but not having a standard C interface is a serious problem for any language.
EPILOGUE:
I do not hate Lisp, and I think it was a fine tool decades ago, and I am not going to say "Lisp sucks". However, now that we have superior languages for coding close to the iron, high-performance computing, number crunching, algorithms, scripting and gluing components together, Lisp should be finally retired.
--
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cybers pace.org | don't, I need to know. Flames welcome.
(blank lines added below to keep my newsreader happy)
nobody wrote: This article is posted at the request of C.W. Yang who asked me to detail my opinion of Lisp, and for the benefit of people like him, who may find themselves intrigued by this language.
You should be shot on sight for posting advocacy to a bunch of
non-advocacy groups. "Thanks" for polluting the groups with yet another
programming language war.
F'up set.
/Thomas no************* ***@yahoo.com (nobody) writes: This article is posted at the request of C.W. Yang who asked me to detail my opinion of Lisp, and for the benefit of people like him, who may find themselves intrigued by this language.
Did he ask you to post this article in these newsgroups?
comp.lang.c++
comp.lang.java. programmer
comp.lang.schem e
comp.lang.c
comp.lang.pytho n
Why did you not post it comp.lang.lisp where it would be at least
relevant?
Due to time constraints, I will refrain from posting any follow-ups here.
If you do not intend to engage in convesation, why are you posting it?
This article is a collection of facts anyone interested in Lisp should know about.
Is there some reason anyone should take `nobody' at yahoo seriously?
Look up "a public apology" thread started by Pascal Costanza as an excellent example.
What does such a personal matter have to do with the language?
I do not hate Lisp, and I think it was a fine tool decades ago, and I am not going to say "Lisp sucks". However, now that we have superior languages for coding close to the iron, high-performance computing, number crunching, algorithms, scripting and gluing components together, Lisp should be finally retired.
You clearly have some sort of axe to grind. If you don't like Lisp,
don't use it.
To others, if you are unfamiliar with Lisp you are welcome to read a
rebuttal in comp.lang.lisp
Please direct all followups to comp.lang.lisp
nobody wrote: This article is posted at the request of C.W. Yang who asked me to detail my opinion of Lisp, and for the benefit of people like him, who may find themselves intrigued by this language.
The solution to your problem is obvious. Just treat Lisp like
Chocolate; if you don't like it, you can't have any.
Followups set.
Bear
I don't know what this post has to do with comp.lang.c, but whatever.
This was pretty funny nonetheless.
As for me, I would say practically the same things about Java. :-p no************* ***@yahoo.com (nobody) wrote in message news:<16******* *************** ****@posting.go ogle.com>... FACT 2: No one but a small clique of fanatics likes it
No matter how odd or perverted the cause, there will be followers. In fact, the odder the cause, the fewer, but more fervent its followers are.
But nobody is more fervent than lunatics whose membership applications
were *rejected* by imaginary little fanatic cliques. Their cause, in
fact, usually has just one follower.
nobody wrote: This article is posted at the request of C.W. Yang who asked me to detail my opinion of Lisp, and for the benefit of people like him, who may find themselves intrigued by this language.
I fail to see why anyone should give a rat's ass about what someone
hiding behind "no************ ****@yahoo.com (nobody)" has to say about
anything. "Nobody"'s opinions about LISP, C, or the color of bananas is
completely worthless. When you have the cajones to stand behind your
opinions, you might be paid attention to.
Something that calls itself nobody wrote:
[snip]
This is an obvious troll. Please ignore it. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Frank |
last post by:
Whats best :
register_globals ON ?
OR
register_globals OFF ?
I currently use:
$_POST
|
by: scorp7355 |
last post by:
I was wondering if there is some other way to turn autocomplete off
besides using "autocomplete=off", using a meta tag or something
similar. It would be great if there is some way to turn it off at a
page level.
Any ideas/thought would be greatly appreciated.
Thanks in advance,
Zac
|
by: nicholas |
last post by:
Although in my web.config I have <customErrors mode="off" /> I still get no
detailed errors.
How comes ?
THX
This is what I get:
Server Error in '/mywebfolder'Application.
|
by: Andreas Müller |
last post by:
Hi!
I've been looking for a way to log off another user from Windows XP, that is
to terminate his session without having to shutdown Windows. My goal is to
write a service (preferrably running under System privileges) which is able
to log off users after a defined time. Since other users may be logged on as
well, it would be quite an unelegant and questionable way to simply use
ExitWindows or something of this kind.
Since the task manager...
|
by: no_spam_for_gman |
last post by:
Hi,
I can turn off autocommit within the command window but I cannot figure
out how to turn it off when you are in the IBM DB2 Command Line
Processor. Does anybody knows how? By the way I mean when you are
logged on and the prompt is: db2 =>
Here's an example how I do it from Command Window (option is c):
| |
by: Frank Rizzo |
last post by:
I have the following situation:
1. Application X1 runs under a regular user account (this user is also
the currently logged on user).
2. Application X1 kicks off Application X2 using an Administrator
account and then quits itself.
3. Application X2 does a couple of things, then restarts Application X1
using the regular User account, then Application X2 quits itself.
|
by: Rory Becker |
last post by:
A wise man once said: "Never put off until runtime what you can fix at compile
time."
Actually I think he said it about 10 minutes before I started this post.
I am a firm believer, like the man in question, in "Option Strict On" by
default.
Actually I don't believe I have code where this is not the case.
|
by: =?Utf-8?B?R3JlZw==?= |
last post by:
We have an application in our office that has the Option Strict option set to
off right now. I do understand it should be set to ON, but right now, I'm
just going to continue with it this way since I do not have the time to fix
everything to set it to ON.
Anyway, my question is if its set to OFF why is it it keeps getting set back
to ON, everytime we move the package from one machine to another. It's the
Option Strict option specific to...
|
by: scooby dooby |
last post by:
Hi All,
I need to write a script for windows,which has the requirements as below.
1,It should log out the particuler user from windows at a particuler time ,say 6 o'clock in the evening everyday,At the same time it should not log off other users.Say, if A and B are the users ,then only A has to be loggef off .Also it should display an alert window before logging off.
Following pop up msg has to be displayed ''you are going to log off ,plz...
|
by: Rain |
last post by:
Hi,
I noticed the other day when I was trying to optimise the traffic on a
particular web page that it had significant viewstate even though I had
turned it off for most of the controls. So in a bold step I decided to
attempt to set viewstate on the form itself off which had a massive impact
on the viewstate like 80K to 15k.
So my question is what is the significance of turning off the viewstate for
the form and what information...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
| |
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
| |
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |