From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: Holy Wars redux: w3 vs. emacs-w3m
Date: Mon, 04 Nov 2002 23:30:12 +0100 [thread overview]
Message-ID: <uwunt2cjv.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: slrnasdjk0.sm.nospam.look@nomad.consult-meyers.com
"A. Lucien Meyers" <nospam.look@replyto.please.because.this.is.invalid> writes:
> alkibiades@gmx.de (Oliver Scholz):
>> "Michael J. Barillier" <blackwolf@pcisys.net> writes:
[...]
>> > Anyone have an opinion[3] on W3 vs. emacs-w3m?
>>
>> IMHO Emacs/W3 feels a lot more emacsish. Well, it is written in Elisp
>> anyways. I really wish it would be more actively developed, because
>> actually it is my favourite browser. And yes, I know emacs-w3m and I
>> use it as a last resort, when Emacs/W3 fails to render a page. I am
>> not happy with this, though.
>
> Why not, Oliver? w3m works and works well. w3 does not. Basta.
*hehehe* I don't think that this "Basta" is well applied on a piece of
free software. :-) I would read that statement rather as "Emacs/W3
still needs a lot of work before it is reliable and usable as your
main browser."
[Actually on my system Emacs/W3 is not reliable only in cases, where
emacs-w3m is not reliable, too: in dealing with images and some
advanced css stuff (Come to think about it, I doubt that emacs-w3m
even tries to address the latter). So the main disadvantage is that
Emacs/w3 is slow. Very slow, to be sure.]
I do not want say anything bad against emacs-w3m, but it feels like
the interface to an external console application. (Probably, because
it is one.) While Emacs/W3 -- slow and incomplete and imperfect as it
may be -- has at least the potential to be a full fledged graphical
(!) web browser integrated in Emacs.
I envision Emacs/W3 as the equivalent to Gnus in the far future: the
slowest but most powerful and extensible html browser out
there. O.k. maybe this is rather dreaming ...
But apart from that, I'd like to see it in a broader context: I am
pretty sure that Emacs will get more and more word processing
facilities in the future. I see Emacs/W3 as a component of the Emacs
Integrated Text Processing and Rendering System. As I read W. Perry's
papers about the future of Emacs/W3, he seems to have something like
that in mind.
It is true that Emacs/W3 has suffered some bit rott, because nobody
seems to develop it actively. But this will not change, if we allow it
to become a public opionion that Emacs/W3 should be disregarded.
Finally the OP got the religious flame war he asked for. :-)
> BTW w3m also works quite well as a stand-alone browser under X.
Outside of Emacs I tend to be a lynx fan.
Oliver
--
14 Brumaire an 211 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2002-11-04 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1036345624.19554.help-gnu-emacs@gnu.org>
2002-11-03 17:55 ` Holy Wars redux: w3 vs. emacs-w3m Adam P.
2002-11-03 18:38 ` Henrik Enberg
2002-11-04 15:19 ` Oliver Scholz
2002-11-04 19:46 ` A. Lucien Meyers
2002-11-04 20:32 ` Henrik Enberg
2002-11-04 22:30 ` Oliver Scholz [this message]
2002-11-04 23:00 ` Oliver Scholz
2002-11-05 5:02 ` Michael J. Barillier
[not found] ` <mailman.1036473338.10358.help-gnu-emacs@gnu.org>
2002-11-05 15:47 ` Jay Belanger
2002-11-05 0:41 ` mr.sparkle
2002-11-05 13:20 ` Sacha Chua
2002-11-03 17:33 Michael J. Barillier
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=uwunt2cjv.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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).