This is a fork of Chicory, a bit more context of the relationship between the projects can be found here:

https://github.com/dylibso/chicory/issues/1296

Any background / context around what the Chicory author means in this comment?

> We'll consider merging in changes that make sense from Endive, but under the stewardship of the [Byte Code Alliance] I have very little faith in its future. My words mean nothing though having all but completely lost interest and use for WebAssembly.

What's the background / history of Byte Code Alliance?

Not everyone is on board with CORBA but with WebAssembly, which is basically what the reboot of the component model is, so probably that.

The AssemblyScript folks have a similar opinion.

yeah that is roughly the concern, many runtimes didn't want to continue on past wasip1, mostly because of the component model.

The comment is from the Dylibso CEO.

It's great to see that since the release of Edge.js [1], they started to take Node.js compatibility more seriously (they went from ~40% to about 75% in just 2 months, so either coincidental or not this is clearly a step on the right direction).

Good work to everyone on the Deno team!

[1] https://edgejs.org/

Are you not tired of self-promotion?

Yeah, the strategy is literally the same

Wasmer (YC S19) | https://wasmer.io/ | Multiple Roles | Remote (EU) or Office (US) | Full-time

We are building the next generation of infrastructure for AI without Docker containers, but with a better container technology based on WebAssembly!

We are hiring for:

  * Rust Engineer (Remote, EU timezone)
  * Rust Distributed Engineer (Remote, EU timezone)
  * Developer Education Engineer (Office, San Francisco)

https://www.workatastartup.com/companies/wasmer

Thanks Yuri. Keep up the good work

Yes it can :)

Yes, this should be fully possible.

We actually believe Edge.js will a great use case for LLM-generated code.

Yes, it could run in iOS (using JavascriptCore, V8 in jitless mode, or QuickJS), although we don't have a prototype app yet.

It should probably take a few hours with AI to get a demo for it :)

Awesome! Are you planning on setting a license soon? I might have missed it but I don't see it on the GitHub repo.

Just set it to MIT :)

It’s not a dumb question at all.

And yes, it will allow running Node.js apps fully on the browser, in a way that’s more compatible than any other alternative!

Stay tuned!

Do you have any specific test case that you would consider "very challenging" on the compatibility side? I'd be curious to check if BrowserPod can support that already.

>in a way that’s more compatible than any other alternative

I can see where that's going.

Awesome. I want to msg. you on LinkedIn but can't.

We are so deep into the weeds that sometimes is hard for us to realize that maybe we are not explaining in the best terms.

What was the most confusing thing in the blogpost? I'd like to polish a bit more to make it clearer! Thanks a lot!

Hi Syrusakbary, I have to admit I still do not fully understand what this is.

First, I could not find usage examples on the edgejs.org page and the docs link points to the node docs, why?

If I head to github, there are some usage examples, but they confuse me more.

The first example: $ edge server.js led me to think that this is a node replacement that runs in a webassembly sandbox, so completely isolated. But why the need of --safe then? What's the difference between using it and not using it?

But the next examples creates more confusion to me: $ edge node myfile.js $ edge npm install $ edge pnpm run dev

What is this doing? I thought that edge was a node replacement, interpreting and running javascript files, but it's now running executables (node, npm)... what is that? What happens when I run npm install... where does it install files? What's the difference between running edge node myfile.js and edge myfile.js?

Hope this helps.

> I could not find usage examples on the edgejs.org page and the docs link points to the node docs, why?

This was intentional, as a demonstration that Edge and Node should not diverge a bit. You should be able to replace `node` with `edge` in your terminal and have things running, so that's why we point to the Node.js docs.

> But why the need of --safe then? What's the difference between using it and not using it?

Edge.js currently runs without a sandbox by default. The main reason for this is two fold: native currently performs a bit better than with the Wasm sandbox (about 10-20% better), and because we wanted to polish more the Wasm integration before offering it as default.

> $ edge pnpm run dev > What is this doing?

This is making the `node` alias available for anything that you put after edge. This allows pnpm to use the edge `node` alias instead of your platform node.

Things will be installed as usual, in your `node_modules` directory