unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuchen Pei <id@ypei.org>
To: "T.V Raman" <raman@google.com>
Cc: Richard Stallman <rms@gnu.org>,
	 Stefan Monnier <monnier@iro.umontreal.ca>,
	 emacs-devel@gnu.org
Subject: Re: Package "luwak"
Date: Sun, 11 Dec 2022 15:04:09 +1100	[thread overview]
Message-ID: <87r0x6fux2.fsf@ypei.org> (raw)
In-Reply-To: <p91ilitp5fg.fsf@google.com> (T. V. Raman's message of "Fri, 02 Dec 2022 18:49:39 -0800")

On Fri 2022-12-02 18:49:39 -0800, T.V Raman wrote:

> Richard Stallman <rms@gnu.org> writes:
>
>
> 1+.
>
> As a likely potential user, I looked at that package and didn't see
> anything there that would improve EWW after a quick review;

This package is not intended as a candidate to merge with EWW. It is a
web browser of its own. Stefan Monnier's rationale for merging it with
EWW is that ideally we should have a backend and a frontend systems for
web browsing, the backend retrieves over the net and parses the
response. The frontend decides how to display the parsed results. It is
conceptually a good idea, but requires a lot of work. For starters, lynx
-dump as a backend provides a plaintext version of the html. It seems to
have a long history and widely used for web scraping. There's no dom or
structure, but only links.

Best,
Yuchen

-- 
Please join me to support free software for a free society:
https://appeal.fsf.org

PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0
          <https://ypei.org/assets/ypei-pubkey.txt>



  reply	other threads:[~2022-12-11  4:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 23:51 Package "luwak" Richard Stallman
2022-12-01  0:52 ` Stefan Monnier
2022-12-02 22:51   ` Richard Stallman
2022-12-03  2:49     ` T.V Raman
2022-12-11  4:04       ` Yuchen Pei [this message]
2022-12-04 23:18   ` Will Mengarini
2022-12-05  4:25     ` Jean Louis
2022-12-05 22:30     ` Richard Stallman
2022-12-06  9:05       ` Philip Kaludercic
2022-12-06 22:37         ` Richard Stallman
2022-12-07  3:33           ` Eli Zaretskii
2022-12-07  7:11             ` Philip Kaludercic
2022-12-07  8:44               ` Andreas Schwab
2022-12-01  3:54 ` North Year
2022-12-11  3:54 ` Yuchen Pei
2022-12-11 23:34   ` Richard Stallman
2022-12-11 13:07 ` Yuchen Pei
2022-12-12 22:19   ` Richard Stallman
2022-12-11 14:29 ` Stefan Monnier
2022-12-11 18:03   ` Tim Cross
2022-12-12 22:19   ` Richard Stallman
2022-12-12 22:42     ` Philip Kaludercic
2022-12-13 23:58       ` Richard Stallman
2022-12-14 21:34         ` Philip Kaludercic
2022-12-14 21:41           ` [External] : " Drew Adams
2022-12-16  3:35           ` Richard Stallman
2022-12-16 15:33             ` Alfred M. Szmidt
2022-12-16 17:31               ` [External] : " Drew Adams
2022-12-16 18:52                 ` Alfred M. Szmidt
2022-12-18  3:21               ` Richard Stallman
2022-12-16 11:05           ` Jean Louis

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=87r0x6fux2.fsf@ypei.org \
    --to=id@ypei.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=raman@google.com \
    --cc=rms@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).