6 ms·
How Python is killing Lisp
- Scriptor 17y agoPersonally, it's the double learning curve of having to learn Lisp and Emacs. I understand the basic concepts of Lisp now, but could someone point me to a good introduction to learning Emacs, Slime, and Lisp all at once? Does Practical Common Lisp do that as well?
- bugs 17y agoThere are certain things that usually just come with practice, emacs and slime usually seem to fit in that category. Once you have gone through the tutorial most of the time you just look up things or figure them out until you remember what to do in a specific situation. There probably are some screencasts for introduction to emacs, slime might have some available as well.
- enum 17y agoYou don't have to learn Emacs. Also, Common Lisp isn't the only option. Try Scheme, this one: www.drscheme.org.
- Scriptor 17y agoThe thing with Emacs is that I feel like I am missing out on the full potential of developing in CL if I'm not using it. How true is that?
- gruseom 17y agoI don't think it has to be true, though they do go together well. Not all CL hackers use Emacs. You might consider trying the Lispworks IDE, or the Allegro IDE (on Windows) or the Clozure IDE (on Mac).
- Locke1689 17y agohttp://www.plt-scheme.org/ http://www.plt-scheme.org/ is the new website. I feel its wrong for me to push this without at least mentioning that one of my professors wrote Dr. Scheme :-/
- alecco 17y agoBut ECMAScript is killing Python. The writing is on the wall.
- alecco 17y agoHello, (former) fellow python fans. ECMAScript, formerly known as JavaScript, is doing very well. So well Python developers started to show their concern for about 2 years. You could read it on PyPy blog and Python mailing lists. The new ECMAScript VMs are getting faster and already beating Python's. And they are getting faster with plenty of room to improve. The language is cleaning up, with a major milestone reached a few days ago. They have the biggest installed base in the world and there are more developers. The language fits in precisely the same slot as Python. The writing is on the wall. Down-voting what you don't like doesn't make it go away and it should be very un-HN. EDIT: Read again the name of the story title if you think my post was flame-bait.
- viraptor 17y agoWell - this comment is quite interesting. The parent one looks like a one-line "meh" comment. I'm quite happy to downvote the original and upvote this one... But is it really killing python? The language is basically the same (almost-dictionary based, easily extensible types / prototypes, etc.). There's a big difference though: afaik there's no real library for ecmascript that would integrate it with the os. There's simply no way to use ecmascript standalone on a typical system. ecmascript is good in places where you need an embedded scripting language, but lua is not enough. Unfortunately neither of them is useful as a general-purpose language right now. Once someone produces a serious repl-like environment and a set of sys / os / file libraries - it can compete with python.
- alecco 17y ago> Well - this comment is quite interesting. The parent one looks like a one-line "meh" comment. I'm quite happy to downvote the original and upvote this one... The original title is a stupid flame-bait and the funny thing is it's a dated argument. [That was my point, turning the flame back.] > There's a big difference though: afaik there's no real library for ecmascript that would integrate it with the os. There's simply no way to use ecmascript standalone on a typical system. What are you talking about? There have been people working with Spidermonkey for ages. Now there are so many V8-based projects it feels almost like a crazy fad. The hello world example of V8 is a shell showing trivial OS integration. > Once someone produces a serious repl-like environment and a set of sys / os / file libraries - it can compete with python. There are plenty of libraries in the making, perhaps the criticism could be there are too many. The thing is, since it's trivial to interface it with C and C++, at the moment most (?) of us are just exploiting the much, much larger library base of those languages. Use whatever language you feel like. In a few years, remember this. I might be wrong, or Python might get its act together, we don't really know. But the writing...
- m0th87 17y agoAs a non-lisp programmer, what scares me away is the syntax. I don't think I could ever wrap my head around the (admittedly succinct) examples I see online, because it takes so much effort for me to figure out what's going on in even a few lines of code. Comparatively, I was able to understand what was going on in most python scripts before I knew the language. Is this something that just takes a while to get down? Or are some people just naturally prone to the syntax?
- PieSquared 17y agoThe reason this syntax scares you is simple: it's different. At the very root, Python syntax is nearly identical to Java, C, etc. The syntax of Haskell, OCaml, etc, is a deviation from that of Python, Java, etc, but not an incredibly significant one. Perhaps you may find that the syntax of these languages scares you but you think you could probably learn it after a bit of mind-wrangling. Lisp, on the other hand, is old. It was developed over 10 years before even C came to being! So the syntax is completely different, and requires you to actually learn it instead of just assuming that your knowledge of other programming languages will pull you through. In summary, it's not a fault in you. It's just that you are used to C-derived and influenced syntaxes, but not to Lisp; and the syntax of Lisp is different enough that you need to actually learn it. Here's a crash course: (f a b c) is the same as f(a,b,c). '(a b c) is kind of like ["a", "b", "c"]. '(1 2 3) is just like [1,2,3] (defun x (a b c ...) ...) defines a function x(a,b,c). (+ 1 2 3) is just like +(1,2,3) = 1 + 2 + 3 (setf x 5) is just like x = 5 '(a b ,c) is just like ["a", "b", c] if L is equal to '(1 2 3), then `(10 20 ,@L) is like [10, 20, 1, 2, 3] Now, to be honest, I just showed you nearly 100% of the 'syntax' Lisp has. The rest is already understanding the language (knowing how to def. functions, how to do loops, etc). By the way, what you might find interesting is that I once showed this to a friend of mine who knew nothing about programming. I showed him how to write a basic program in Java (with a few subroutines and a loop), then how to do it in Lisp. He exclaimed, "Argh! If I can do it like this, then why do I need all those fancy weird words like public and void and what not and braces and... eugh!" Sorry for that longish post, I hope you found it at least a bit informative. ;)
- tel 17y ago
- mark_l_watson 17y agoI wrote 2 Springer-Verlag Lisp books in ancient times, and have about 25 years of Lisp experience. That said, Ruby has mostly replaced Lisp in my toolbox. When I do use a Lisp family language, it is most often Gambit-C Scheme to build small standalone executables - and sometimes Franz or SBCL Common Lisp. BTW, I consider Python and Ruby to be fairly interchangable - use whichever you like best. Both are great languages with great libraries and supporting open source projects.
- garnet7 17y ago> Ruby has mostly replaced Lisp in my toolbox. Wow. Would love to hear why. Could you list some of your weighted plusses and minuses for Lisp and Ruby?
- mark_l_watson 17y agoI used to worry more about good runtime performance. Now I prefer to use a language that is easier and faster to use in development. re: pluses and minuses: Lisp: + better interactive development style; I'll keep a Lisp repla open most of the day. For Ruby, irb is not something that I live in. + really great runtime perfromance - not as many libraries for web frameworks, database, etc. Ruby: + very concise and fun to develop with + many great libraries and frameworks - poor runtime performance
- mahmud 17y agoMark, you're a polyglot. I would say for the last 20 years you have been a C++, then Java author more than a Lisp programmer. The first C++ book I ever owned was yours, the one about artificial agents that had a sculpture on the cover, and that must have been 15 years ago. If you're in the business of education, your "toolbox" is essentially whatever people need to learn. You wouldn't hear an English teacher in Korea with 25 years of experience saying she is done teaching English, because teaching Spanish is so much more easier. That doesn't make any sense. At the time you wrote the published Lisp books, it was the height of AI-bubble and people needed to learn Lisp and Prolog. Then you wrote an Smalltalk book (IIRC.) then C++, Java .. all dictated by what the public needed. Btw, you still have the literary and expository prowess to teach today's hot technologies as well. But that doesn't say anything about Lisp, Prolog, Smalltalk, C++, or Java except that you are no longer in the business of teaching them. And I mightly thank you for the Agents book, btw. I didn't know what I was doing and just typed in the code into Borland C++ 4.5. The diskette was missing when I bought it, and I am sure I tried to download the source code from the Addison-Wesley ftp site (it could have been a Prentice Hall book as well) Cheers!
- whyenot 17y agoPython also wins because it's a living language, still changing, adapting and updating itself while Common Lisp died the day the ANSI standard was published and today is a zombie, even if it still smells fairly nice. Now that comp.lang.lisp is utter crap, there isn't much of a community either except for #lisp, which as an outsider I find kind of intimidating and not a good place to ask for help. Actually, what lisp really needs is for Conrad Barski to clone himself 10x :)
- cema 17y agoWell, there is always Clojure, as another commenter mentioned. Its community is different (friendly and helpful) and so is the language (vibrant, modern and evolving).
- mnemonicsloth 17y agoThree years old. When this was written, there was no such thing as Clojure [1], and a number of now-essential CL libraries were just getting started. Providing no new information, this article just invites needless soapboxing. [1] Clojure is fast, free, trendy, inherently parallel, and fits seamlessly into the Java ecosystem. It's just an anecdote, but I notice less complaining about parentheses, too.
- cema 17y agoYou are correct. Still I think it offers useful historical perspective.
- mnemonicsloth 17y agoLisp already has too much historical perspective. That's one of the things people like about Clojure.
- camccann 17y agoIt's just an anecdote, but I notice less complaining about parentheses, too. I still like the idea of "Lisp with syntactic whitespace". A few simple transformation rules to add implicit parentheses based on indentation would make it a lot more readable for people who aren't already veteran Smug Lisp Weenies. There was even a specification written for adding it to Scheme: http://srfi.schemers.org/srfi-49/srfi-49.html http://srfi.schemers.org/srfi-49/srfi-49.html
- ynniv 17y agoIt didn't feel needless when I wrote it. The lisp community was sitting on their haunches (their laurels had long rotted away), and silly new languages were stealing lisp's thunder. Today, I would probably have written about how clojure will soon be "killing" python, so maybe I'm just a soapboxer.
- kristianp 17y agoI started learning scheme recently, and enjoyed it for a while, then went back to ruby. (I have been programming in Ruby for a few years now.) If I want to prototype something quickly, I will use ruby. I think the modular way you can program in an oo language is another factor. It is easy to write a demo, and then add the class to a rails project. I tried to read about using modules, such as those used by gambit-c, but the mailing list replies were dense with jargon, which I found more of a barrier than the parentheses. I found the scheme environment too fragmented and lacked a decent equivalent of rubygems. The lack of a non-emacs editor with nice indenting was a contributing influence. Replace ruby with python and scheme with lisp above, to see the relevance.
- deleted 17y ago[deleted]