GNU Emacs Development Inefficiency

By Xah Lee. Date:

Posted a bug about a problem in minor modes. bug#6611 However, it got closed within a min it was published, and wrongly!

It got closed right away i suppose partly has to do with my unforgiving nature of criticizing and run-in with some GNU emacs developers in gnu.emacs.help and comp.emacs in the past 5 or so years.

It's quite frustrating trying to contribute to GNU Emacs. In the past 3 years, i've submitted some 50 bug reports i think by now … without looking at the records, i think at least 10 or so are hard bugs that got fixed. Some of my outspoken criticisms, had their effects, and i suppose some emacs 23's UI changes are influenced by my criticisms. (e.g. line-move-visual, text selection highlight by default, and i noticed yesterday that emacs 23.2.1's doc now removed the phrase “real-time display editor”, which was a item i criticized in Problems of Emacs's Manual.)

I've also written to Richard Stallman a few times in private in about 2008 or 2009, about documentation improvements. With extreme politeness and respect on my part. Without going into detail, i'm just disenchanted by his reaction. In short, it appears to me he did not pay much attention, and basically in the end asked me to submit changes to him. Yeah right. The whole shebang seems to be very well described by Ben Wing. [see GNU Emacs and XEmacs Schism, by Ben Wing] (Richard Stallman's emails are pretty short, just a couple terse sentences; but he does, however, whenever he got a chance, tell his correspondents to use the term GNU/Linux, and ask them to contribute.)

Re-writing the whole doc in a modern perspective might take me one month full time. (For example, 160 hours) But if it were to be done in a public way, or submit to him, the time it takes to communicate, email, write justifications, create diffs, …, can easily take half a year full time (960 hours). In the end, i'm not even sure half of the text in the new doc would be accepted.

The GNU Emacs's bug database sucks. (it's using Debbugs.) The web interface/presentation is incomprehensible. I have problem finding all bugs posted by me or by a bug number. The several times i used it, i still haven't figured out how to find a bug given its bug number. (haven't really tried hard, but to search by bug number or by poster should be something one would intuitively know how to do within 30 secs of browsing the site.) They did not have a bug database, only in around 2008. Most commercial software have a bug database system in 1990s, and most large open source projects have one by early 2000s. (I wrote a bug tracker in 1998, 4k lines of Perl (with CGI, MySQL), in about 2 weeks, for a startup brainpower.com.)

Am pretty sure there are several good “FSF Free” bug databases. [see Comparison of issue-tracking systems] Few years ago, some may have problem to be politically qualified to be “Free” for FSF to adopt. However, these days there are many that FSF officially sanctions as “Free”. However, when you look at FSF, you see that even when a software became FSF Free, they usually are still picky with lots qualms, and typically always ends up using their OWN ones (i.e. from GNU project), even though it is clear that it is inferior. (the GNU emacs dev's revision control system was CVS up to ~2009. CVS has been phased out in early 2000s in majority of software orgs or projects. (GNU emacs now uses Bazaar (BZR). since 2010.)

These are consequence of old and large orgs, with its old policies and bureaucracies. See: “Free” Software Morality, Richard Stallman, Paperwork Bureaucracy.

Who are the main developers of FSF software these days? Mostly, they are either paid as FSF employee, or students still trying to break out their craft in programing, or 40 or 50 years old semi-retired programers who otherwise isn't doing anything. Those willing and able, spend time and get decent salary in commercial corps, or went to start their own projects or business that'd be far more rewarding financially or recognization than being another name in FSF's list of contributors.

These days, FSF and Richard Stallman more serves as a figure-head and political leader in open source movement. FSF's software, largely are old and outdated (For example, unix command line utils), with the exception of perhaps GCC and GPG. If we go by actual impact of open source software in society, i think Google's role, and non-profit orgs (such as Apache, Perl, Python, PHP, Ruby, various languages on JVM), and other commercial orgs (For example, Apple, and other commercially founded project hosters for hosting open source projects (Google Code, SourceForge, github, etc.)), exceeded FSF by early 2000s.

Thanks to Alan Mackenzie [http://www.emacswiki.org/emacs/AlanMackenzie] for correction on revision control system used by GNU Emacs.

See also: Emacs Dev Inefficiency and Emacs Web 2.0?.

Emacs Modernization

  1. Simple Changes Emacs Should Adopt
  2. Why Emacs Keys are Painful
  3. Problems of the Scratch Buffer
  4. M-key Notation vs Alt+key Notation
  5. Menu Problem
  6. Mode Line Problem
  7. cua-mode Problems
  8. kill-buffer Induces Buffer Accumulation
  9. Emacs Form Feed ^L
  10. Inconsistency of Search Features
  11. Single Key to Delete Whole Line
  12. Emacs HTML Mode Sucks
  13. Emacs Does Not Support Viewing Images Files In Windows
  14. Emacs Spell Checker Problems
  15. Adopt HTML as Texinfo Replacement
  16. Support HTML Mail
  17. Problems of “man” Command
  18. Emacs Lisp Mode Syntax Coloring Problem
  19. Emacs Ahk Mode Problems
  20. Problems of Emacs's Manual
  21. Problems of Emacs's Manual; Examples
  22. Emacs: Have You Read Emacs Manual?
  23. Elisp: Ban Syntax Table
  24. Emacs: Make elisp-index-search use Current Symbol
  25. Emacs: Usability Problems of Mode Documentation
  26. Problems of Emacswiki
  27. Emacs GNU Texinfo Problems; Invalid HTML
  28. A Record of Frustration in IT Industry; Disappearing FSF URLs, 2006
  29. Emacs Manual Node Persistency Issues
  30. Emacs: dired-do-query-replace-regex Replace ALL (fixed)
  31. Problems of Emacs Supporting Obsolete Systems
  32. Elisp: Function to Copy/Delete a Dir Recursively (fixed)
  33. Thoughts on Common Lisp Scheme Lisp Based Emacs
  34. Text Editors Popularity and Market Research
  35. Text Editor's Cursor Movement Behavior (emacs, vi, Notepad++)
  36. GNU Emacs Development Inefficiency
  37. Emacs Dev Inefficiency and Emacs Web 2.0?
  38. Letter-Case Commands Usability Problems
  39. Emacs: Select Line, between Quotes, Extend Selection
  40. Emacs: isearch Current Word
  41. Suggestions on Line Wrap Commands
  42. Emacs: Single Key to Delete Whole Line
  43. Emacs Cult Problem: Emacs vs Windows Notepad
  44. Emacs Undo and Emacs Cult Problem

If you have a question, put $5 at patreon and message me.
Or Buy Xah Emacs Tutorial
Or buy a nice keyboard: Best Keyboards for Emacs

Emacs

Emacs Lisp

Misc