YC News Unavailable...

Re:YC News Unavailable... by shadowplay on Friday September 28, 2007 @02:02AM (#60461)

This seems to be a recurring theme with Lisp implementations. Reddit switched from CMUCL to Python (threading); Vendetta Online switched from SBCL to Erlang (GC/memory leaks). Other people have hit major snags e.g. with Haskell/GHC runtime bugs (Wager Labs; switched to Erlang). Use a massively complex runtime, hit bugs that can't be fixed (in a start-up timeframe, anyhow)?

[ Parent | on HN ]

Re:YC News Unavailable... by Kaizyn on Friday September 28, 2007 @02:12AM (#60467)

If more people used LISP runtime systems, then the bugs would be found more readily. Thus leading to fewer defections from LISP to Blubs.

[ Parent | on HN ]

Re:YC News Unavailable... by davidw on Friday September 28, 2007 @06:13AM (#60528)

"positive network externalities:

http://www.welton.it/articles/programming_language_economics...

One of the reasons we try and convince other people to use our tools.

[ Parent | on HN ]

Re:YC News Unavailable... by shadowplay on Friday September 28, 2007 @03:03AM (#60476)

Not necessarily -- some organizations would patch it themselves in a private branch just to maintain an edge, assuming they have the expertise in-house. I've done this before with GPLed libraries. That's assuming you can even track down the problem -- Vendetta Online couldn't pin it down well enough to submit a coherent bug report (in fairness, SBCL is a monstrosity; just as a comparison, how many Rails developers could track down CRuby bugs?).

I wouldn't call Erlang and Python Blubs.

[ Parent | on HN ]

Re:YC News Unavailable... by dfranke on Friday September 28, 2007 @03:48PM (#60794)

> how many Rails developers could track down CRuby bugs?

Probably a lot of them, if they tried. Because Ruby is so poorly specified, I frequently read the interpreter source code to figure out how things are supposed to behave. CRuby is really well-written in some ways and really poorly-written in others. It's poorly written in the sense that it's a painfully slow line-by-line interpreter. It's well written in the sense that the code is very clean and well-organized: I can usually find answers in the source faster than I can find answers in the pick-axe book.

[ Parent | on HN ]

Re:YC News Unavailable... by shadowplay on Friday September 28, 2007 @04:04PM (#60802)

My impression is most Rails developers are not C programmers.

[ Parent | on HN ]

Re:YC News Unavailable... by pg on Friday September 28, 2007 @04:39PM (#60811)

No, turns out the system was just running out of memory.

[ Parent | on HN ]

Re:YC News Unavailable... by shadowplay on Friday September 28, 2007 @07:55PM (#60890)

I hate it when facts don't agree with my theories.

[ Parent | on HN ]

Re:YC News Unavailable... by brlewis on Friday September 28, 2007 @09:31AM (#60579)

This is a recurring theme with cutting-edge software. Arc is probably exercising parts of the mzscheme code that haven't been exercised before. Bugs will be fixed and things will be better.

[ Parent | on HN ]

Re:YC News Unavailable... by dfranke on Friday September 28, 2007 @02:36PM (#60732)

I rewrote my senior project in Common Lisp two weeks before the due date because I was running into too many bugs in mzscheme. Then I switched from clisp to SBCL because of a bug in clisp.

[ Parent | on HN ]

Re:YC News Unavailable... by euccastro on Friday September 28, 2007 @09:26PM (#60923)

Reddit switched from CMUCL to Python (threading)

Source? With the bashing Python is getting because of the GIL, it surprises me that someone would switch to Python from elsewhere for any reasons related to threading.

[ Parent | on HN ]

Re:YC News Unavailable... by shadowplay on Tuesday October 02, 2007 @09:18PM (#62381)

> Source?

Straight from PG:

"Incidentally, the last straw, I've been told, was some bug in CMUCL threads that kept making the system crash."

http://groups.google.com/group/comp.lang.lisp/msg/574d19d5e7...

From Reddit: http://blog.reddit.com/2005/12/on-lisp.html

[ Parent | on HN ]