abarth

On iOS, the code that you've modified runs in an interpreter but code you haven't changed runs the existing fully optimized AOT code that's already in your app.

Thanks!

Fuchsia has a lot of Rust code. (Disclosure: I write Rust code for Fuchsia on a daily basis.)

There are some similarities. The main difference is that Wine is mostly in-process whereas, in this design is mostly out-of-process. I'll add a section on Wine to the "prior art" section of the doc.

Disclosure: I wrote the doc linked above.

The memory model is similar (a flat, linear address space). The OS APIs are quite different. Fuchsia's OS APIs are designed around an object-capability discipline. For example, almost all the syscalls take a zx_handle_t as their first argument, which means they are operations on an object the process has previously been granted access explicitly. In Linux, many OS APIs operate on the "ambient" environment rather than on a specific kernel object.

Disclosure: I work on Fuchsia.

Ah, I didn't realize the comment above was about the Eng Council. I'll raise the issue at our next meeting. Thanks!

I'm sorry, but I'm not sure what you mean by "this manifest." The blog post linked above was written by Wayne Piekarski, who is a Developer Advocate for Fuchsia. My role in the project is as a software engineer.

I look forward to it!

I understand where you're coming from, but that ends up being an inclusion issue in the project. I'm comfortable having my name and bio "out there" on the Internet, but I recognize that's a privilege. Not everyone who contributes to the project will be comfortable doing that.

Thanks! Yes, your ideas are alive and well in the project.

As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)