From: David Kastrup <dak@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: a look at the browser scene & emacs
Date: Wed, 25 Feb 2009 11:28:45 +0100 [thread overview]
Message-ID: <86wsbeajz6.fsf@lola.quinscape.zz> (raw)
In-Reply-To: 8358de80-5198-41e5-b4a2-04e681d359d1@p20g2000yqi.googlegroups.com
Xah Lee <xahlee@gmail.com> writes:
> News about the browser world
> http://www.macworld.com/article/139022/2009/02/safari4firstlook.html?t=232
>
> emacs really needs to keep up.
>
> The IDE idea, from 1990s to 2000, basically reduced emacs market share
> from perhaps more than 50% in the early 1990s to maybe 1% today among
> professional programers.
>
> emacs today has lots of problems. Many of the “emacs way”, are
> technically inferior. But the nice elisp system holds it back still.
>
> The way for emacs to advance, is to get more people to use emacs.
> Emacs users today are already just the very small clique, half of
> which are perhaps over 40. With these small circle of people, every
> idea that's not “emacs way” gets stamped out.
Or gets adapted to the Emacs way. The result is that people get one
consistent tool.
> Emacs 22 took a few major step, by having syntax highlighting on by
> default, and CUA mode as a option. Emacs 23 took it further,
Emacs 23 is not yet finished.
> by having cursor move by visual line, and have highlight selection on
> by default. I presume that in emacs 24 might have CUA mode on by
> default...
It quite certainly won't.
> but these changes are happening quite late.
> The emacs on the mac, in particular Aquamac emacs and Carbon emacs,
> did significant job in saving emacs from oblivion.
I disagree. That's something only a Mac-centric person could say. The
cross-platform upstream code foldback has been minimal.
> There are a lot needs to be done, especially on the Windows platform
> because it is used by most people.
Platform-specific additions are a dead end since they tend to be
single-person efforts that die out once the person can't be interested
anymore.
--
David Kastrup
next prev parent reply other threads:[~2009-02-25 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 5:18 a look at the browser scene & emacs Xah Lee
2009-02-25 10:28 ` David Kastrup [this message]
2009-02-25 13:13 ` Xiao-Yong Jin
2009-02-25 22:26 ` Samuel Wales
2009-02-25 23:14 ` Xiao-Yong Jin
[not found] ` <mailman.1758.1235567636.31690.help-gnu-emacs@gnu.org>
2009-02-25 13:26 ` Richard Riley
2009-02-26 8:57 ` Miles Bader
2009-02-26 9:42 ` Xah Lee
[not found] ` <002094c7-f9fd-422e-a68f-67051e0c7483@w9g2000yqa.googlegroups.com>
2009-02-26 9:59 ` Tassilo Horn
[not found] ` <87k57dwmay.fsf@thinkpad.tsdh.de>
[not found] ` <go5qmt$a7e$1@news.sap-ag.de>
2009-02-26 11:23 ` Tassilo Horn
2009-02-28 15:48 ` Colin S. Miller
2009-02-28 18:12 ` Samuel Wales
2009-02-25 17:49 ` Xah Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wsbeajz6.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).