4 ms·
Lisp was a lot less web friendly then than it is now, especially compared to those languages.
by ilikehurdles 7y ago
Lisp was a lot less web friendly then than it is now, especially compared to those languages.
- toyg 7y agoIn primitives, yes; but that's not the point with Lisp, whereas it is for those alternatives.
- mark_l_watson 7y agoWhen Alexis Ohanian gave a talk at Google in 2013 I asked him afterwards about converting Reddit from Common Lisp to Python. He said the Common Lisp version crashed too often. He even made a funny comment about this when he autographed Without Their Permission for me. I agree with you, the web apps in CL story is much better now. I am biased, now that I am mostly retired most of my fun side projects are in CL (with Haskell being a close second). I really don’t care what languages other people choose to use but using CL makes me happy and I enjoy reading about other people doing good things in CL.
- namibj 7y agoDo you know of any good setup for type-aware autocompletion of Haskell? There are some language servers for it, but it's difficult to get them to play nicely in the face of updates and such. I hope such an editing system could offset the power of AST macros due to the possible ease of discovery. Macros unfortunately require a very skilled developer team to not cause mayhem, taken to the extreme in Go not offering any fancy typing or macros.
- hajile 7y agoI doubt crashing had anything to do with lisp -- the site crashes hard at least once every week. It was all about logistics. YC had two competing companies. They pushed them together. The lisp team could get up to speed on python faster than the python team could on common lisp.