From: Qiantan Hong <qhong@mit.edu>
To: "rms@gnu.org" <rms@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: About implementing libre.js/el in Emacs
Date: Mon, 31 Aug 2020 04:13:58 +0000 [thread overview]
Message-ID: <F11775A2-A2FD-453B-AFB7-F19417A593FE@mit.edu> (raw)
In-Reply-To: <E1kCawY-0005VV-Oy@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
>> 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.
>
> This is a bad idea, at the deepest level, because it means supporting
> Emacs extensibility in two separate ways, with separate
> implementations. That would make Emacs far more complex.
>
> We should not support Emacs extensibility in Javascript.
>
I highly agree with that, however currently numerous browser extensions
are already implemented completely in Javascript, including LibreJS.
Maybe another option is to have the other way around, implement
a JavaScript to Elisp translator, and support Emacs Lisp version of
those web extension APIs. Then we can run the translator on librejs
to get librejs.el as a starting point.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1858 bytes --]
next prev parent reply other threads:[~2020-08-31 4:13 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
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 [this message]
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=F11775A2-A2FD-453B-AFB7-F19417A593FE@mit.edu \
--to=qhong@mit.edu \
--cc=emacs-devel@gnu.org \
--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).