Re: too many buffers

[Elena]

On Dec 2, 4:51 pm, "Pascal J. Bourguignon" <p...@informatimago.com>
wrote:
> Elena <egarr...@gmail.com> writes:
> > On Dec 2, 7:58 am, Tim X <t...@nospam.dev.null> wrote:
> >> A major mistake made by new users is to try and make emacs like every
> >> other editor or even like an IDE. This is a mistake.
>
> >> Emacs is liked by many because it is very different. Others don't like
> >> the difference and for htem, it is not the right editor. However, if you
> >> start by trying to make it just like everything else your use to, you
> >> will miss the opportunity of experiencing something different and new
> >> which may turn out to be better than what your familiar with - provided
> >> you give it a chance.
>
> > Problem is: this Emacs uniqueness is not documented anywhere.  All
> > IDEs look alike because they follow a design pattern which works.
> > There are tons of usability studies done on this.  OTOH, how would you
> > develop a project following the Emacs way?  Nobody knows.  Every
> > Emacser reinvents the wheel.
>
> No, no, no.  It's the others who reinvented the wheel.  Emacs was there
> before the GUI IDE. They could have copied emacs (or the Lisp Machine),
> but no, they had to reinvent the wheel...

Pascal, we have fought on this kind of issue already.  Yes, others
reinvented the wheel, but they progressed from there afterwards.
Emacs lagged behind.  Now, I understand that old-time users of Emacs
are comfortable enough with it and don't want to leave it, and Emacs
can be pushed way beyond what other editors ever could, but please,
let's not call it an IDE, because it is just an editor.  Ehi, have we
ever read the Emacs manual?  Here it is its very first sentence:
"Emacs is the extensible, customizable, self-documenting real-time
display ***editor***."  It says "editor", doesn'it?

An IDE is an ***Integrated*** Development Environment.  If you have to
wrestle with tons of settings to have something resembling an modern
IDE - as you have with CEDET - then your tool is not an IDE.  Period.

What many programmers fail to realize about IDEs is that a lot of
knowledge about usability is required to develop a productive IDE, a
knowledge which is beyond the capabilities of the average programmer,
or even the experienced one.  Please, let's not confuse a bloated IDE
with a nice one.