WebAssembly

And then we had Cosmos.

causing WASM-related issues that caused more problems.

And it was just really hard to get things going, which is why we've decided to focus on stability that was being so prohibitive to launching new features like XMR.

Focus on stability, get everything right, get everything churning, get everything trading, like all these things, so that we can get back to normal and continue to ship features like XMR, for example.

Usually straightforward, this is a documentation addition in the section of the documentation where we describe those projects out there that are compatible with Zephyr and that can easily be pulled into Zephyr as modules.

WebAssembly micro runtime is one of them.

So it's a project on GitHub, I think, originating from Intel originally.

And it is easy to use it in a Zephyr context.

And WebAssembly on embedded, we've heard about it for quite a while now.

I wouldn't know off the top of my head like i said i haven't tried it um i'm not sure how like how small things um things can get but uh it's um it's an interesting um it's an interesting idea and um yeah turning it on enabling it is as always just a couple of k configs so um like really cool stuff and the license is it's apache license with llvm exception

So you can download a Chanko WebAssembly and execute it on a core.

Is that what you're saying? And you can access the Zephyr API, obviously, if you have them mapped, I guess.

And it takes advantage of our ability to compile to JavaScript.

It takes the ability of the fact that our compiler is a native binary, and we've compiled it to Wasm.

So the whole thing runs inside your browser.

And it takes you on a tour through every single language feature.

And we wrote this really cool technology.

We basically wrote an operating system that runs in WebAssembly in your browser.

Very nerdy stuff, but like.

No one had ever done it before.

And so they said, "We are in the process of disclosing these two vulnerabilities to the maintainers," meaning the Chromium guys.

Okay, so of course, V8 is Google's open source, high performance JavaScript and WebAssembly engine used internally by Chrome, uh, other Chromium, uh, browsers, Node.js, and other projects.

And as we also know, it recently received an extremely high volume of updates thanks to automated vulnerability disc- uh, discovery.

So this allowed OpenA...

If it brings major syntax changes, it could become impossible to maintain a single WordPress version compatible with both PHP 7.4 and PHP 9.

The rest of the talk revolved around tightening ties with the PHP project, resuming the conversation about WebAssembly, which was once dismissed due to lack of interest, but now makes more sense given WordPress's existing use of Wasm in Playground, bringing WordPress's HTML API work to PHP rather than keeping it internal only.

And the idea, still at wishlist level, that plugins with unsafe dependencies could be loaded with restricted permissions, marking as untrusted any code depending on them.

As concrete follow-up, there's talk of reviewing whether the distribution of old WordPress versions itself has changed and exploring sending automatic warnings to plugin developers when their code isn't compatible with a given PHP version.