News for hackers. Stuff that matters.
Re:GNU HURD: Altered visions and lost promise by hga on Wednesday June 30, 2010 @12:22PM (#1475332)
The "canon" official FSF GCC effort failed, at least in that it was replaced by a bazaar model fork: http://en.wikipedia.org/wiki/GNU_Compiler_Collection#EGCS_fo...

As noted by tl, EMACS suffered a nasty fork, and it bears pointing out that RMS started with a fully functional version of EMACS written by none other than James Gosling of Java fame. RMS replaced Gosling's MockLisp with a real Lisp (both bytecoded), but the guts remained largely the same.

Re:GNU HURD: Altered visions and lost promise by eru on Wednesday June 30, 2010 @04:49PM (#1476175)
I wouldn't consider EmacsLisp a real Lisp any longer. At least by modern standards. But anyway, I agree.
Re:GNU HURD: Altered visions and lost promise by hga on Wednesday June 30, 2010 @05:00PM (#1476215)
Is not the big difference dynamic vs. static scoping?

That was a matter of much debate that started to conclude when RMS did GNU Emacs, in 1984 when Common Lisp was also officially released for the first time, the latter's biggest breaking change perhaps being static scoping.

Were you thinking of anything else?

Re:GNU HURD: Altered visions and lost promise by eru on Wednesday June 30, 2010 @05:10PM (#1476251)
I thought only of the dynamic scoping. I just found out that Emacs Lisp doesn't have tail recursion optimization, thus dooming you to use side-effects (because recursion can't be used for loops).

But I also understand that Lisp isn't a family of function languages. Functional is just a style that's possible and encouraged in Lisp, not required.

Re:GNU HURD: Altered visions and lost promise by hga on Wednesday June 30, 2010 @06:07PM (#1476401)
Well ... Scheme is the only big Lisp that guarantees TCO, while Clojure provides a recur special form plus a syntax for mutual recursion, since the JVM as of yet does not directly support TCO.

Obviously some (many?) implementations of Common Lisp provide it, but I'm not sure it's something you can particularly depend upon (I got out of the Common Lisp community in ... 1984 and haven't seriously used it since then).

Then again, I myself wouldn't necessarily describe Common Lisp as a modern Lisp anymore, it's essentially been frozen in amber when it standardized and it's filled with legacy cruft, perhaps most especially it being a Lisp-2. Scheme's standardization process has become glacial, but there is one (well, two, RnRS and the SRFIs). Clojure is much like Lisp Machine Lisp in the early days, although it should be past the worst of breaking changes by now.

Re:GNU HURD: Altered visions and lost promise by kiba on Wednesday June 30, 2010 @01:45PM (#1475571)
Yet emacs somehow not managed to die from the fork.