5 ms·
Emacs doesn't seem to be much of a failure. The GCC is used by everyone. However, admittedly, they are written by RMS himself.
by kiba 16y ago
Emacs doesn't seem to be much of a failure. The GCC is used by everyone. However, admittedly, they are written by RMS himself.
- loup-vaillant 16y agoOf course GNU is successful in some areas. I suspect he was talking about kernels only?
- alec 16y agoI suspect he was just trolling.
- tl 16y agoThose are examples of projects succeeding in spite of GNU. We had the Emacs/XEmacs schism, where rms fought against lucid over features, most of which are in emacs now. How many people actually like gcc? Why is Apple pushing to replace it (see LLVM / clang) when they can play nicely with cups or khtml?
- mahmud 16y agoThere was also a GCC "schism", remember EGCS? It was a fork of GCC by a tight-knit group of core developers.
- loup-vaillant 16y agoWell, in that case, EGCS won, and was renamed GCC…
- ZeroGravitas 16y agoI was under the impression that they wanted to use llvm in their proprietary IDE (amongst other proprietary apps) which would rule out GCC for purely licensing reasons.
- jonhohle 16y agoXcode is already (and has always been) a wrapper around gcc/gdb. Clang provides a cleaner interface for integrating with an IDE (among a lot of other things).
- koenigdavidmj 16y agoYes. In addition, LLVM provides a much nicer interface to get symbol tables and things like that---another boon to Xcode.
- hga 16y agoThe "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_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.
- kiba 16y agoYet emacs somehow not managed to die from the fork.
- eru 16y agoI wouldn't consider EmacsLisp a real Lisp any longer. At least by modern standards. But anyway, I agree.
- hga 16y agoIs 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?
- eru 16y agoI 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.
- hga 16y agoWell ... 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.
- avar 16y agoI use Emacs to do all my editing. But I think it's a failure compared to what it could have been. There's nothing inherent about Emacs that ties it to being an editor, it could have been rewritten a long time ago in Scheme or acquired a FFI. Then things like GNOME or TextMate might have been rewritten as part of the Emacs ecosystem, while looking exactly like they do today. Instead Emacs is a very specific thing to a small crowd, and adding things like a FFI to it have been vetoed by Stallman in the past. That's one of the reasons I think that we still don't have Lisp as a first-class systems programming language on GNU as the initial announcement promised: http://www.gnu.org/gnu/initial-announcement.html http://www.gnu.org/gnu/initial-announcement.html GCC is much the same. There was a proposal many years ago to make a libgcc. Stallman vetoed that on the basis that things like C++ support might be written without contributing the changes back to the FSF. That's a fair point, but LLVM+Clang are quickly replacing GCC in some areas due to its monolithic architecture. You can't write things like a C source code using GCC as a backend (easily), but you can with the LLVM tools.
- kiba 16y agoInstead Emacs is a very specific thing to a small crowd, and adding things like a FFI to it have been veto-ed by Stallman in the past. That's one of the reasons I think that we still don't have Lisp as a first-class systems programming language on GNU as the initial announcement promised: http://www.gnu.org/gnu/initial-announcement.html http://www.gnu.org/gnu/initial-announcement.html So RMS failed in one execution for a still extremely excellent toolkit that would have make the GNU project even more well known for its excellent technical quality. If anything, the GNU project is a great tremendous success, even if it is sometime dogged by its own short-term political interests. If he didn't listen to his political interest and instead focus on technical quality of his work, he would have achieved something much greater for the GNU project and his movement.
- avar 16y agoIt certainly has a lot of inertia. But most of its big projects started in the old days are huge monolithic codebases that are starting to lose favor for various reasons. Emacs because not everyone likes the UI (and it's impossible to replace it, unlike other parts), GCC because Clang+LLVM are more modular and reusable, automake because it's a huge and hard to learn mess while newer systems aren't etc. It's also losing some users like Apple and the BSD's due to the GPLv3 switchover. I think that in the long term the GNU project will become increasingly irrelevant due to most of their crown jewels being hard to maintain, and there being political opposition to changing that.