Build a JS Runtime in Rust

Build your own JavaScript runtime with Rust.
Read along here: deno.com/blog/roll-your-own-j...
Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.
Website: deno.land
GitHub: github.com/denoland
Discord: / discord
Twitter: / deno_land

[@ashishkumawat6110]

"Let's build a runtime" proceeds to install prebuilt runtime libraries 😶

[@wlockuz4467]

Yo dawg, I heard you like building frameworks, so we put a framework inside a framework so you can build a framework while you use a framework.

[@SRG-Learn-Code]

Wait.. Awesome? What are you doing here?

[@ChichaGad]

Just wrapping wrappers with wrappers lmao

[@dinoscheidt]

😂

[@awesome-coding]

👋👋👋

[@anyadatzaklatszjutub]

@@awesome-coding❤

[@jearsh]

is this a runtime, or is it a rust program using deno as a runtime?

[@tryoxiss]

A runtime created where the engine is a binding to V8 and the event loop is a binding to Deno. So its less of a runtime and more just glue, but whats what most devs write anyway.

[@thejoycode]

It uses deno as a runtime, and then builds a wrapper around it using rust... So it's a runtime built on a runtime + rust. So it's just deno with extra steps

[@markoffden]

Imagine showing this to doctors while they kindly accompany you to your ward nodding “yes, sure mate, a-ha”

[@kakashi_69_xd]

Awesome.. waiting for the series

[@duckmasterflex]

The new running joke is "you have a working library in Javascript? lets write it in rust"

[@ricko13]

This is the kind of videos I watch when I have the need to procrastinate 😴

[@mike110111]

This is so great! Thank you

[@programmersoham]

let's dig into it

[@justy1337]

Music to my ears :)

[@PaulPhilp-pe5oe]

The voice is awesome!

[@1001bit]

tho an indian accent

[@xNiqueish]

@@1001bit I'd say scandinavian one

[@silloi]

Yes it gets quite better than those uploaded before

[@heycherry100]

so awesome! more more more!

[@ShravanSunder]

Yea, more please!

[@peterhayman]

yes very interested!

[@Ma1ne2]

Well, this is COOL!

[@narrei666]

my first thoughts was whether ryan dahlis awesome or its just a deal

[@rbdm]

If this series ever gets updated it might be interesting to see how to pass existing data from from Rust to JS and back

[@krtirtho]

Aghh.. now u have unlocked this new domain of writing infinite amount of runtimes to the JS community. Now, we've to suffer the consequences.

[@Disorrder]

Cool! But how about TS runtime?

[@sayedulkrm]

I need to watch this video after 10 years 😅 Right video wrong time

[@pitust]

Wouldn't a dedicated scripting engine be a better job for the task than a copy of V8? Especially since v8 is absolutely massive, and plugins are not the hot code path anyway (or they shouldn't be at least). IMO, an embeddable scripting language like starlark or even just a copy of QuickJS would work much better than v8 (and also it would not be a 50 megabyte codesize increase, which is also fun)

[@AZisk]

Fireship too $$$$

[@jeffreyjdesir]

this seems insanely powerful...whatever it meant to be a pc developer probably applies even less now

[@Imscottirl]

It’s not that big a deal. He’s just lifting deno.

[@ncubica]

@@Imscottirl mmmm more than that it is containerizing deno, so technically if you were using something like Tauri you could have a embeded REPL as simple as this video?

[@Imscottirl]

@@ncubica that’s fair, and a solid use case. I’ve embedded V8 directly, so I guess that’s why I’m a little meh. V8 integration will change your life. Almost zero docs, a 50mb library, and cryptic exceptions.

[@mike110111]

Hmm the core api has changed a lot since the blog post was written (July 2022) so the code doesn't work anymore!

[@deno_land]

We should revisit our blog post and update it accordingly. Thanks for pointing that out.

[@michiplays7142]

Is there any reason to make your own runtime instead of using node or deno directly?

[@ncubica]

REPL ? imagine running automate script that user can write, you can have them sandboxes on a deno instance? i mean you could use deno directly. I don't know I just trying to make a sense of this video lol...

[@eineatombombe]

said in the beggining, it's to learn

[@leeroyjenkins0]

​@@eineatombombeLearn what? Not to make a runtime, clearly. Since you're using one as a library

[@leeroyjenkins0]

But indeed, there are some valid examples at the start for why you would want to do this. It allows you to interact with JavaScript directly from rust instead of having to spawn a process and communicate with it. Plugins/user scripts would be a common one, you can modify the context of the engine as it's running and get whatever values you'd like from it fairly easily.

[@eineatombombe]

@@leeroyjenkins0 im not talking about what was done in the video. the question was `why make a runtime` not `why "make" a runtime by installing a few libraries`

[@jagadeeshgade6309]

❤

[@YordisPrieto]

Oh no no no! What have you done ✅ Deno! What have you done! Freaking Pog

[@MikeKasprzak]

Wow

[@nanashi7726]

1:26 This code does not work in the latest deno_core

[@deno_land]

Thanks for pointing that out. We will update our content accordingly.

[@abubalo]

This video was scheduled to be released on April 1, but, well, here we are

[@friendlywavingrobot]

Someone get React Server Components running now

[@nm6x]

Please expand this subject… show us how would you add nom modules…

[@Funcijej]

Do you mean npm? Or is nom modules just something I haven’t heard of yet?

[@nm6x]

@@Funcijej npm lol!

[@vanvothe4817]

Wait...I hear fireship in here

[@eineatombombe]

no this is awesome www.youtube.com/@awesome-coding

[@rezwanahmedsami]

He he lol

[@taquanminhlong]

Well, this still lacks setTimeout and other global declarations, on top of that, v8 rust API is not easy to use at all 😂

[@MurderByProxy]

do one in C

[@anonymoussloth6687]

What's better? Deno or bun? I heard bun is faster

[@SimonBuchanNz]

Different projects with different goals. Bun is selling itself nearly entirely on being fast, while Deno is trying to do Node "right": Rust to make the embedding safe, an extensibility model like you saw here with ops and extensions to build the entire runtime API, so you can easily add or remove whatever features you want in your own version of the runtime, a new and better package registry, built in typescript, watch, tests and building (many of which got copied back into node), a new standard library.... It's trying to do way more things. Being fast is laudable, but if that was really your *only* goal, then really you shouldn't be using JavaScript. And there's been a few of misrepresentitive claims about just how fast Bun is, comparing nonequivalent actions etc.; you shouldn't actually expect noticable performance differences most of the time. That said, why not just try both? They're all fairly compatible.

[@eineatombombe]

bun is faster, but doesn't support everything. and when you install a node package in bun, it will use node APIs so it won't be faster

[@TRLYx]

FIRST I AM THE COMMENT KING