Any plan for the FFI?
Nice work! But as an embeddable engine, I think it would also be nice to provide some API functions for the other languages to use.
This would be an interesting addition. I would do it in a different crate in the workspace, with only the FFI, using boa as a dependency.
We could use cbindgen crate to automatically generate C/C++ FFIs.
And it would be better to provide more accessibility to the engine, like https://duktape.org/api.html
New Guy here. I'm sniffing around this. I think the problem here is going to be more one of defining scope and granularity. Like I think just implementing an eval is one thing, but those fine folks at duktape have a dukload of things they expose. Making it similarly comprehensive for Boa is probably... hard. But I can take a whack at eval in its own FFI crate.
We discussed this in our triage and we agreed that we wanted to experiment with the diplomat tool first before commiting to an FFI interface, since it makes the maintenance work more manageable.