[HN Gopher] Roll your own JavaScript runtime (2022)
___________________________________________________________________
Roll your own JavaScript runtime (2022)
Author : mikece
Score : 45 points
Date : 2023-02-15 22:48 UTC (1 days ago)
(HTM) web link (deno.com)
(TXT) w3m dump (deno.com)
| rcme wrote:
| The actual runtime is deno_core::JsRuntime
|
| So it's not really fair to call this "your own runtime." quickjs
| is another alternative here, and you can use it anywhere that
| supports the C FFI.
| intelVISA wrote:
| the Deno V8 wrapper doesn't have the same marketing ring
| [deleted]
| [deleted]
| DDSDev wrote:
| I apricate the time that the deno team has spent having a
| separation between deno/deno_core/deno_runtime. The deno codebase
| is well organized and overall high quality.
|
| One issue I've run into as someone who has embedded these
| libraries into another other project is that there are a lot of
| really nice features are only available in deno proper
| (everything under their cli/ directory
| https://github.com/denoland/deno/tree/main/cli) vice deno_runtime
| and deno_core. Specifically, typescript is implemented in cli/
|
| A user of runtime or core could just reimplement those features
| piece meal, however I ended up just forking deno and adding a
| lib.rs that just exposes the code in cli/ as a library, and it
| has worked out pretty well for my needs.
| fatboy wrote:
| Can you tell us a bit about a project you've embedded it in?
| Was it done to provide a scripting interface to an application?
| Something else?
| DDSDev wrote:
| It was an emacs fork that used TypeScript/Javascript
| alongside elisp. I am currently in the process of upgrading
| to deno 1.30.3 right now.
___________________________________________________________________
(page generated 2023-02-16 23:00 UTC)