News for hackers. Stuff that matters.
Re:Why Reddit switched to Python (2005) by lordlicorice on Sunday April 08, 2012 @10:07PM (#3815560)
> After spending the entire summer working entirely in Lisp, it's nearly impossible to work in another language and not say to myself, "If only this were Lisp..." Lisp has many goodies that make programming in it a joy: the REPL, macros and the lack of syntax are some. I won't go into the details, but rest assured, it's cool. People become Lisp zealots for a reason.

I honestly don't understand this sentiment. For me it's nearly impossible to work in lisp and not think "If only this were some other language..." The baseline functionality I'm used to from other languages, like even type checking, is absent. It's like writing in assembly just for the degree of control you have as compared to managed code. I mean yeah writing something in assembly can be fun in its own way, but the result will almost certainly be awful, and you'll solve problems that have built-in solutions in other languages.

Re:Why Reddit switched to Python (2005) by waqf on Sunday April 08, 2012 @10:31PM (#3815592)
I guess you code in ML/OCaml/Haskell the rest of the time.
Re:Why Reddit switched to Python (2005) by zachbeane on Sunday April 08, 2012 @10:52PM (#3815631)
Common Lisp has type checking.
Re:Why Reddit switched to Python (2005) by SeanLuke on Monday April 09, 2012 @03:15AM (#3816111)
Come on, we all know what he meant.
Re:Why Reddit switched to Python (2005) by zachbeane on Monday April 09, 2012 @07:11AM (#3816484)
I don't really know what he meant, with the references to managed code and assembly language in relation to Lisp, but what he actually wrote is wrong when it comes to Common Lisp.
Re:Why Reddit switched to Python (2005) by jbester on Monday April 09, 2012 @08:44AM (#3816713)
Perhaps he's referring to the batteries included feel of other platforms. Every other platform (i.e. .NET/java/ruby/python) have gobs of built-in functionality in the standard library - everything from parsing, to different I/O models (NIO in java), to frameworks (WSGI, WS consumption and production, etc). Lisps diverge fundamentally (e.g., the threading model) if it isn't specified in CLtL or ANSI CL. CL seem hamstrung by those documents.

Concrete Example: 7 years ago I couldn't (using available libraries) reliably parse in lisp a DB dump in XML (~8GB), select some records based on a set of calculations, and convert it to CSV. Most libraries insisted on needing the whole document in memory, some libraries leaked like a sieve and caused heap exhaustion, others couldn't handle UTF8. In the end, I could do it python (couple hours to develop and took 45-60 minutes to run), I could do it in java (several hours to develop and ran in ~8min), but I couldn't do it in LISP without writing a custom XML parser or delving into FFI. Maybe it was an abnormal case, maybe not.

I miss macros and the expressiveness; I miss the community; I don't miss the insanity.

Re:Why Reddit switched to Python (2005) by zachbeane on Monday April 09, 2012 @09:03AM (#3816782)
Well, it's not like that any more. There are portable ways to work with threads, there are multiple XML libraries, some of which do not read the whole document in memory, and all implementations support UTF-8.

These things happened because some people decided to improve CL (both implementations and libraries) instead of using something else.

Re:Why Reddit switched to Python (2005) by jbester on Monday April 09, 2012 @11:13AM (#3817289)
It may be worth retrying as an experiment to see how lisp fairs now.
Re:Why Reddit switched to Python (2005) by rbanffy on Monday April 09, 2012 @09:55AM (#3816936)
You should always pick the right language for the job. You could have written the right language in Lisp or you could pick a good enough language to solve the problem.

Good enough is good enough.

Re:Why Reddit switched to Python (2005) by rbanffy on Monday April 09, 2012 @09:52AM (#3816929)
Stop thinking about writing programs and start thinking about building a language to write your program in. That's Lisp.

If you approach Lisp the same way you'd approach C or Python, you'll fail.