Re: Is Lisp a Blub?

On Jul 2, 3:24 am, Slobodan Blazeski <slobodan.blaze...@xxxxxxxxx>
wrote:
There's many libraries that are relatively easy to find and
install,iterate, series, cells, qi....For a lot of the other mentioned
there is a library already ready to use or code exist or as in call/cc
feature is questionable, some like it some believe it doesn't worth.
So you already have a most powerfull toolbox from any other
lanaguages, you only need to build with it.
The only thing that I really believe that lisp is missing is erlang/
termite like concurrency, but time will tell.
For now we only need more apps written in it.

I work at a university, and just out of curiosity I sat in on a talk
given by young Apple employees to CS students considering applying
there for internships or jobs.

In response to a question about how to present one's self in an
interview at Apple, one of the speakers replied (paraphrase) "Whatever
you do, don't say Mac OS X is perfect. If you can't find anything
wrong with it, how could you possibly have any chance of making it
better?"

I think that would be a healthy attitude to take towards Lisp, or,
frankly, anything else you like. If you think you have found any
piece of utopia on this Earth, you are probably either deceiving
yourself or need to raise your standards.

Now, to your credit, you do mention the concurrency thing. But do you
really think there is nothing else that could make Lisp better?

And with the reliance on the idea that "you can always add that as a
library" you come close to the Godwin's Law of Referencing Turing
Completeness [1].

To avoid hypocrisy, here are some criticisms I made about Lisp:

http://programming.reddit.com/info/1z8b8/comments/c1zbmr

These are more criticisms of Common Lisp culture and community, and I
think most of the weaknesses of Common Lisp reside there as opposed to
something in or not in the text of the standard itself.

-jimbo

[1] http://programming.reddit.com/info/21vs0/comments/c022160

.

Relevant Pages

  • Re: Modernizing Common Lisp
    ... >> the major open source implementors, library builders ... > dictactor to decide on new standards. ... Will Newman and all the effort he put into making SBCL work? ... to Common Lisp" and "knowledgeable about it". ...
    (comp.lang.lisp)
  • Re: ILC2005: McCarthy denounces Common Lisp, "Lisp", XML, and Rahul
    ... > Major improvements would be new programming paradigms. ... > I think the negative effect of standards is not a real one - noone ... "Common Lisp as a dialect arose because institutions with a large ... Interlisp because it appeared to have the largest installed base, ...
    (comp.lang.lisp)
  • Re: Modernizing Common Lisp
    ... I don't think any standards get universal acceptance. ... were folks who were using Lisp around the time of Common Lisp's ... What I any standards process does is add a layer of "Intelligent ... I proposed CL-PPCRE as the current ...
    (comp.lang.lisp)
  • (not so) New Cello Screenshot! [was Re: Yaaawwwwwwwnnnnnn [was Re: Modernizing Common Lisp}]
    ... screen self-capture widget hides itself for a frame so ... and the frame rate, which appears in red at the top left of the window. ... Welcome to the standards process. ... I suggest you put down On Lisp, ...
    (comp.lang.lisp)
  • Re: Modernizing Common Lisp
    ... VB is not a good analogy for Common Lisp. ... It's not like CLISP doesn't WANT to be multithreaded, ... And that "whatever reason" could very well be standards. ... I can get for my Linux machine -- whether or not I pay for it. ...
    (comp.lang.lisp)