unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Qiantan Hong <qhong@mit.edu>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: About implementing libre.js/el in Emacs
Date: Sat, 29 Aug 2020 14:10:03 -0700	[thread overview]
Message-ID: <ab301a29-4a02-0da6-bb91-0f1f4b97ffdb@cs.ucla.edu> (raw)
In-Reply-To: <791FBE67-B71F-4F80-810D-BE29B55FD10C@mit.edu>

On 8/29/20 12:14 PM, Qiantan Hong wrote:
> Option 1, besides enabling libre.js, can also bring numerous existing
> cross-browser extensions to Emacs, if we finally support a large enough
> portion of the Web Extension API. However those extensions are
> all written in JS and JS is worse than Elisp.
> 
> Option 2 might require as much work as option 1, but without the additional
> benefit (or drawback?) of bringing other JS extensions.

I'd suggest Option 1 as providing more bang for the buck. I think the FSF tech 
staff is looking at LibreJS; see 
<https://www.fsf.org/blogs/sysadmin/coming-soon-a-new-site-for-fully-free-collaboration>.



  reply	other threads:[~2020-08-29 21:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 19:14 About implementing libre.js/el in Emacs Qiantan Hong
2020-08-29 21:10 ` Paul Eggert [this message]
2020-08-30  2:26   ` Tim Cross
2020-08-30  2:45     ` Qiantan Hong
2020-08-30  7:44       ` Tim Cross
2020-08-30 14:13       ` T.V Raman
2020-08-31  3:53         ` Richard Stallman
2020-08-31  4:11           ` Qiantan Hong
2020-08-31  4:15             ` Stefan Monnier
2020-08-31  4:17               ` Qiantan Hong
2020-08-31 13:48           ` T.V Raman
2020-09-01  3:22             ` Richard Stallman
2020-08-31  3:57     ` Richard Stallman
2020-08-31  3:57 ` Richard Stallman
2020-08-31  4:13   ` Qiantan Hong
2020-09-01  3:24     ` Richard Stallman
2020-08-31  4:24   ` Qiantan Hong

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=ab301a29-4a02-0da6-bb91-0f1f4b97ffdb@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=qhong@mit.edu \
    /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).