They say hell hath no fury like a lisp fan scorned. I wonder if they hadn't been acquired, would they have still used Lisp ?
We switched to python about 4 months into the startup and a full year before getting acquired.
Selective memory I guess.
81–90 of 118 posts
They say hell hath no fury like a lisp fan scorned. I wonder if they hadn't been acquired, would they have still used Lisp ?
We switched to python about 4 months into the startup and a full year before getting acquired.
Selective memory I guess.
Earlier quoted context omitted.
I upvoted just because it's a neat, historical document that I missed the first time around. I have no particular stake in Lisp or Python.
Yep, I knew that Reddit was originally written in Lisp and made the change to Python at some point. It is neat to learn exactly why and how.
Earlier quoted context omitted.
I think OP meant a writeup about the switch from web.py to Pylons. I'm not sure we ever wrote that one down.
Point! I think I found it http://www.redditblog.com/2007/08/its-slow-its-unstable-its-... Also just as anemic as the last one. Oh well.
What Lisp webserver was used, originally? Hunchentoot? What web servers/stack are Lispers using these days?
What Lisp webserver was used, originally? Hunchentoot? What web servers/stack are Lispers using these days?
Just wondering (as someone who only uses/touches Python indirectly, through some projects that use it, but is not currently a 'Python developer' by any means); was this posted in response to some recent drama in the Django community, or as an argument against Lisp? I'm just wondering why it seems this story is quickly getting upvoted on the front page of HN, when it seems there are no other frontpage stories remotely…
"was this posted in response to some recent drama in the Django community" What drama?
web.py never really worked well, so we ended up rewriting it again. The interesting thing was that Django still wasn't up to the task when we did that, mostly because it's templating engine was too slow. So we chose Pylons instead. It should be noted that Django has since fixed that issue.
Earlier quoted context omitted.
Keysersosa answered this better below, but basically maintainability. There was no writeup, I guess because doing write-ups about internal software switches wasn't really a thing back then. :)
Yeah I think that post dates from a time where you still heard people refer to them as "weblogs". Edit: Found it. It was the 14th post on our blog a time, but definitely light on the implementation details. http://www.redditblog.com/2005/12/on-lisp.html
About this: ===If Lisp is so great, why did we stop using it? One of the biggest issues was the lack of widely used and tested libraries. Sure, there is a CL library for basically any task, but there is rarely more than one, and often the libraries are not widely used or well documented.===
If Clojure was available back then and if you had written it in Clojure instead of Lisp (and given that Clojure can leverage JVM based libraries) - would you still have continued using Clojure?
I know this is an extremely hypothetical question but I am trying to figure out if Lisp is finally getting ready for "mainstream" adoption because Clojure is bootstrapped of the libraries of Java.
The first Python web framework I used was Django. I'm really glad I came across it first because I was inexperienced at the time and it forced me to adopt a lot of good practices. However, now that I'm more experienced, I can relate a little to what Aaron is saying here. Learning all of this boilerplate stuff is annoying! Recently, I started contributing to a friend's rails app and I found the process of learning how…
I wonder. How popular is Pyramid? I ask because I found Pyramid to be quite intimidating the first time (I'm not an exprienced Python developer). It took me four attempts to finally 'get' it - the first three times giving up in frustration and leaving it alone for 2-3 months before trying again. Now that I get it though, it seems like an interesting framework but not a productive one. I've only dabbled in Pyramid wit…
The first Python web framework I used was Django. I'm really glad I came across it first because I was inexperienced at the time and it forced me to adopt a lot of good practices. However, now that I'm more experienced, I can relate a little to what Aaron is saying here. Learning all of this boilerplate stuff is annoying! Recently, I started contributing to a friend's rails app and I found the process of learning how…
I wonder. How popular is Pyramid? I ask because I found Pyramid to be quite intimidating the first time (I'm not an exprienced Python developer). It took me four attempts to finally 'get' it - the first three times giving up in frustration and leaving it alone for 2-3 months before trying again. Now that I get it though, it seems like an interesting framework but not a productive one. I've only dabbled in Pyramid wit…
I also know http://www.cars.com/ is heavily powered by Pyramid.