From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] from the Skunkworks department
Date: Thu, 28 Dec 2017 20:48:16 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1712282015210.24564@carhart.net> (raw)
I hope everyone is having a good holiday season. I've been working on
edbrowse over the past couple of days, but fooling around with experiments
that may or may not lead somewhere. Well that's what led to the use of
esprima and escodegen for deminimizing code, which has been wonderful, so
it leads to great things sometimes.
So the project I've been playing with recently is called JS Interpreter.
https://github.com/NeilFraser/JS-Interpreter.git
https://neil.fraser.name/software/JS-Interpreter/docs.html
A demo is here:
https://neil.fraser.name/software/JS-Interpreter/index.html
It's a sandboxed javascript interpreter written in javascript. It has a
step(). It remains to be seen if it will lead to insights that lead to
real work, but it certainly is fun and informative. Basically it's like a
javascript debugger, with no need for a bloated GUI like firebug,
everything can be examined using ok(), and even the code of the debugger
itself is accessible to modify or echo both the subject-matter javascript
and the debugger's-own javascript. I love it!
Pull it up if you feel like relaxing with something edbrowse-related yet
potentially just for fun. You may have ideas for how we can use it.
K
next reply other threads:[~2017-12-29 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 4:48 Kevin Carhart [this message]
2017-12-29 6:56 ` Karl Dahlke
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=alpine.LRH.2.03.1712282015210.24564@carhart.net \
--to=kevin@carhart.net \
--cc=edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).