Re: Really dumb LISP question.
- From: Fred Waldstein <f.waldstein@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Jul 2009 23:18:28 -0400
Paul Donnelly wrote:
Tetrahedral Quartz <t.quartz@xxxxxxxxx> writes:
Paul Donnelly wrote:Such as a REPL, or another source file?Or a navigation aid.
It's a clean interface. Very little screen space is wasted by thingsIt is if your users prefer to be able to see where they are and where
that aren't what I'm working on, and everything takes place in buffers,
which largely use a consistent set of commands. Emacs isn't my perfect
environment, but it's got the right design principles. The kind of
design that produces one of your “modern” IDEs is just insanity, based
on habit rather than clear thinking. Of *course* toolbars and tabs and
menus and tree views and panes and panes and panes are the way to make a
program. That's how everyone else does it, right?
they're going/can go. If they prefer flying on instruments only,
esp. in a dense fog bank near terrain, then I guess emacs is for
them. :)
If their code is a dense fog bank near terrain, I think they have bigger
problems then their choice of text editor!
I don't think he meant the code was a dense fog bank near terrain. I think he meant the code was the terrain, and having to use instruments in a dense fog bank is what using a text editor instead of an ide is like. My own metaphor would probably have been looking at the codebase through a keyhole with no way to see (let alone navigate using) an overview, but it really amounts to expressing the same feeling in different ways.
Even keeping a dired buffer on the side emacs makes me feel like I can see the trees, but I can't see the forest. Especially when I work on java projects, because of all the different packages and java mandating a different directory for each one. Using a normal IDE lets me have a visual tree of the project's sources at left, and I can find things in it very very quickly, much quicker than by messing around in an emacs dired buffer, or typing in paths directly and possibly making a mistake doing so. With anything OO it's even better since a normal IDE can have that left pane show a class hierarchy instead, or similarly. It's a browser optimized for finding parts of a code base instead of a browser merely optimized for the more generic case of finding files on a filesystem.
So my preference is for a regular old IDE, and I use emacs (or, yuck, maybe even resort to vim) only if I have to remote edit over ssh for some reason.
.
- Follow-Ups:
- Re: Really dumb LISP question.
- From: Paul Donnelly
- Re: Really dumb LISP question.
- References:
- Really dumb LISP question.
- From: Bryan
- Re: Really dumb LISP question.
- From: ccc31807
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: vippstar
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: Tim Bradshaw
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: Tim Bradshaw
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: Paul Donnelly
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: Paul Donnelly
- Re: Really dumb LISP question.
- From: Tetrahedral Quartz
- Re: Really dumb LISP question.
- From: Paul Donnelly
- Really dumb LISP question.
- Prev by Date: Re: Really dumb LISP question.
- Next by Date: Re: Really dumb LISP question.
- Previous by thread: Re: Really dumb LISP question.
- Next by thread: Re: Really dumb LISP question.
- Index(es):
Relevant Pages
|