help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: if vs. when vs. and: style question


From: Emanuel Berg
Subject: Re: if vs. when vs. and: style question
Date: Tue, 31 Mar 2015 18:49:52 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)

Rusi <address@hidden> writes:

> I wrote: Hey! Emacs (Elisp) is civilized!
> followed by definitions of ...

Just because something is more specific, supposedly
advanced (in isolation), and possible to do (of course
it is), it doesn't mean it is a good idea.

Fore example: HTML mails instead of ASCII ditto, LaTeX
homepages (i.e., PDF files) vs. HTML, GUIs vs. CLI,
the mouse vs. the keyboard - all more recent,
supposedly more advanced methods, all possible, and
realized long ago.

Question: But then, why do so many people still don't
like them, and won't use them?

Answer: If you keep it simple, stick to the basics,
then the limit is on you - and, if you master the
basics (which you never do, completely, which is
natural, and a good thing), then the *sky* is the
limit. But: if you master the GUI, the GUI is
the limit!

This is why the people who use the basic, simple, but
combinable stuff are much better at computers, because
they don't put chains on themselves to crop their
creativity, activity, and energy. Even tho the basic
stuff is more difficult day one, very soon the
specific-stuff-people will hit the ceiling, a ceiling
which doesn't exist for the basic-stuff-people - their
ceiling is their own dedication and energy, and as
long as they have that, they are on an
upward trajectory.

Just look: You already discuss what chars are
included, what chars should be included, and so on.
So the limitation is what chars you can and can not
print?! That is bizarre! The ASCII people have
everything they need and the limitation is their own
mental-physical capacity, which they can constantly
push one centimeter upwards for every step they take.

-- 
underground experts united
http://user.it.uu.se/~embe8573


reply via email to

[Prev in Thread] Current Thread [Next in Thread]