News for hackers. Stuff that matters.
Re:How Python is killing Lisp by alecco on Saturday December 12, 2009 @09:03PM (#992245)
> If it is ECMAScript, then the writing is mostly on the browser. Python's writing, however, is everywhere, including the wall.

"The writing is on the wall" is an expression not meant to be taken literally.

> So I would say this killing argument is premature.

Actually many of us are working with ECMAScript outside browsers, often coming from Python and similar languages. Interfacing from C and C++ to V8 is incredibly easy. Have you ever tried to make Python modules?

Also ECMAScript VMs have plenty of security features that come extremely handy, like security. Python security, in particular sandboxing, is almost impossible to achieve and the work-arounds you need kill performance even further.

As a former Python fan, I could go on and on for pages. But I doubt this would change your mind so it's preposterous.

Re:How Python is killing Lisp by sreque on Sunday December 13, 2009 @12:58AM (#992477)
When you tried sandboxing python, did you look at http://wiki.python.org/moin/How%20can%20I%20run%20an%20untru...? There's multiple sandboxing options listed there.

Also, Python has SWIG, SIP, and Boost to help integrate native code. I haven't yet integrated python and C, but I have integrated Ruby and C. A quick google for V8's C/C++ interface is not leading me to anything useful. Is it really that much easier? If so, that's an advantage of the V8 runtime, not of ECMAScript the language itself. Both Python and Ruby have multiple implementations for which native code interface can work differently. Pypy, for example, claims to have a simple libffi interface.

Re:How Python is killing Lisp by cema on Saturday December 12, 2009 @09:11PM (#992260)
Oh, I agree that ECMASCript is a wonderful language which is widely misunderstood and underestimated (not in this community, but in the industry in general). However, there is more to a successful language than just the "linguistic" quality, or else Lisp would not be where it is now.
Re:How Python is killing Lisp by mcav on Saturday December 12, 2009 @09:14PM (#992263)
> "The writing is on the wall" is an expression not meant to be taken literally.

I think that was satire.

Re:How Python is killing Lisp by alecco on Saturday December 12, 2009 @09:42PM (#992291)
I tried to take it that way but since the meaning of the expression is godly written messages of upcoming doom it didn't make any sense. For satire to be funny it has to [follow], or at least mirror, in some way the original meaning. I picked he isn't familiar with the expression to the alternative, that he failed at being witty.