Re: Python 1 , Lisp 0
- From: Jon Harrop <jon@xxxxxxxxxxxxxxxxx>
- Date: Thu, 01 Oct 2009 21:32:09 +0100
Dave Searles wrote:
Jon Harrop wrote:
Lisp lacks static typing, is slow to run, impossible to parallelize (due
to the lack of any Lisp implementations with concurrent garbage
collectors, even among commercial offerings), comparatively
uninteroperable and has no libraries comparable to WPF, XNA, LINQ and the
TPL.
Bull***. One Lisp, Clojure...
I was talking about Common Lisp.
has a concurrent GC,
Not by default.
specific support for parallelism,
Anything comparable to the lock-free work stealing concurrent deques of the
Task Parallel Library?
and is interoperable with the huge existing body of Java
libraries and code.
Anything comparable to the robustly-deployable hardware accelerated 2D and
3D vector graphics of Windows Presentation Foundation?
Furthermore, a version has been made for the .NET
runtime which has the same concurrency support (modulo concurrent GC in
the .NET runtime) and access to the same libraries your precious F# has
access to.
They only just fixed value types in Clojure yesterday. You can hardly
compare that to something that Microsoft are going to release as
fully-supported production-quality software in a few weeks...
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?u
.
- Follow-Ups:
- Re: Python 1 , Lisp 0
- From: Dave Searles
- Re: Python 1 , Lisp 0
- References:
- Re: Python 1 , Lisp 0
- From: Jon Harrop
- Re: Python 1 , Lisp 0
- From: Dave Searles
- Re: Python 1 , Lisp 0
- Prev by Date: Re: Python 1 , Lisp 0
- Next by Date: Re: Python 1 , Lisp 0
- Previous by thread: Re: Python 1 , Lisp 0
- Next by thread: Re: Python 1 , Lisp 0
- Index(es):