all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Qiantan Hong <qhong@mit.edu>
Cc: Tim Cross <theophilusx@gmail.com>,
	 Paul Eggert <eggert@cs.ucla.edu>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: About implementing libre.js/el in Emacs
Date: Sun, 30 Aug 2020 07:13:02 -0700	[thread overview]
Message-ID: <p91imd01att.fsf@google.com> (raw)
In-Reply-To: <B49DA191-8109-47DF-A30B-D9DB984E73A8@mit.edu> (Qiantan Hong's message of "Sun, 30 Aug 2020 02:45:26 +0000")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1928 bytes --]

Qiantan Hong <qhong@mit.edu> writes:


1+ for the elisp side.

Here are a few more things to think about:

Looking forward or Looking Back?

Most of the Web's "web apps" are written in JS, but I suspect much of
that will also fall outside the bounds of what RMS calls "ethical JS".

At the same time, having  a "web in emacs extension language" might
allow us to imagine, invent, and create a whole new class of
collaborative interactions that the so-called mainstream Web might never
think of or create -- and in that sense, a prototyping/extension
language that aligns with elisp might serve us better.

In thi scontext, I'd also like to point at the Nyxt browser which uses
parenscript  (Lisp that compiles down to JS) as an  another example of
using Lisp to script the Web.

https://common-lisp.net/project/parenscript/
>> On Aug 29, 2020, at 10:26 PM, Tim Cross <theophilusx@gmail.com> wrote:
>> 
>> Just curious - in what ways is JS worse then Elisp? 
> There¡¯re lots of other arguments, e.g. homoiconicity, typing (js does lots of
> unreasonable type casts)¡­ but in this context, I think the most important
> point is that Emacs and Emacs Lisp give one of the most flexible and
> self-descriptive programming system. If something is implemented in
> Emacs lisp, we get M-x apropos, describe-function, describe-variable,
> they can be overrode by just eval-defun, and can be advised. Customizing
> or extending it is painless and trivial. However, those things become
> much harder if the package is implemented in JS.
>
>> I agree Option 1 would give more bang for your buck - at least initially. 
>> 
> I¡¯ll take that. I imagine while implementing Web Extensions API for js
> it will be trivial to also bring those to Elisp too, so finally we not only
> have those JS browser plugins to run but can also develop plugins
> in Elisp.
>

-- 
7©4 Id: kg:/m/0285kf1  •0Ü8



  parent reply	other threads:[~2020-08-30 14: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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p91imd01att.fsf@google.com \
    --to=raman@google.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=qhong@mit.edu \
    --cc=theophilusx@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.