You dismiss Emacs and others as "not the future" too readily. You should not be as interested
in the future so much as in the past. Specifically, you want to re-use libraries and code.
But you decide to reinvent some of the more painful parts. That seems to be a long-running
trend in programming, and I wish it would end.
Hotwire seems really cool, but I (for one) would greatly prefer seeing the effort go into
extending and perfecting an existing system. Some of the benefits you list don't apply to me;
I already *have* re-usable pipes and buffers in Emacs, process and directory editors, image
thumbnails, and an interactive D-Bus interface. And a mail and news client, document viewers,
web browsers, debuggers, and more. Not everything is perfectly integrated, but that's a
byproduct of so many years of success.
As your list shows, Emacs isn't the only other project that could use your effort and vision.
It is unfortunate that you decided not to help any of those.
(And xterm has a GUI portion also: the Tektronix window. It's been there a long, long time,
but few programs still can use it.)
Posted Jun 26, 2008 22:44 UTC (Thu) by walters (subscriber, #7396)
[Link]
I've contributed some nontrivial patches to Emacs and was in the past a core committer. Don't
get me wrong, Emacs is great and has left a lasting impression on me.
However, while it makes sense to have a good relationship between one's interactive
shell/toplevel and one's editor, I don't think it necessarily makes sense for them to be the
same thing always.
Emacs' fundamental architecture at this point is just too limiting; Emacs Lisp is far behind
the times. The buffer-oriented display technology lets one easily do some neat things and
lends itself very well to a keyboard-oriented control (which is crucial for a good
programmer's editor).
But Emacs doesn't have anything like GtkTreeView.