4

Modular JS/execution engine · Issue #30863 · servo/servo · GitHub

 5 months ago
source link: https://github.com/servo/servo/issues/30863
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Comments

Member

Can we make our JS integration modular, and general? See attached document for a start of the discussion. Servo--modular JS engine.pdf

A checklist(of only one item for now):
jokeyrhyme reacted with thumbs up emoji

gterzian

added B-meta This issue tracks the status of multiple, related pieces of work modularity

labels

Dec 12, 2023

gterzian

added the L-javascript Javascript is required label

Dec 12, 2023

Member

Just found this: #21371

Member

Author

Just found this: #21371

Thanks for sharing, it's an interesting approach to making the script crate generic: it seems to make script generic over some it's internals, like the dom parser and tokenizer, but it does not seem to deal with how script integrates with externals such as Spidermonkey or Layout. At least that is what I make of it after a quick read.

Like I mention in the PDF attached at the top, I think we first need to isolate how Spidermonkey is used, because obviously one cannot make script generic to all of the use of js::jsapi and js::rust that you can see all over script. But an end-goal would see script being generic over a code execution engine, in a similar way to how the linked to PR make script generic over the tokenizer and parser.

It could be worth revisiting that PR, although it would be a separate effort from the one this issue is focused on.

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK