Upcoming Servo Triage and Embedding meeting Dec 23 2024

[gterzian]

Where: https://meet.jit.si/ServoTriage.

When: 10:00 AM UTC

What: any issue one wishes to triage, or embedding related issue one wished to discuss

Who: anyone is welcome, but if there are no issues to discuss the meeting will be canceled.

Please express your interest to attend and note the issue(s) you would like to triage(which can be one someone else already brought up).

Last meeting at #112

Action points:

• Mini-apps updates.
• Readablestream updates. Implement Streams servo#34676
• Idea: Make Servo embeddable in an application that is rendered using wgpu
• Modular JS/execution engine servo#30863

[gterzian]

For mini-apps, a good starter is at https://github.com/espinr/miniapp-components/blob/main/docs/explainer.md

[nicoburns]

@gterzian Ah, that's very helpful. Is the idea to standardise on one format (unifying the various implementations in that document)? Or to create foundations that support each of them separately?

[LaraineShen]

• Capabilities In The MiniApp Scenario：

In the MiniApp scenario, the ROM size is usually required to be small enough.
Capabilities such as audio, video, and bluetooth usually use native (operating system) capabilities.
Can these be configured not to participate in compilation during code compilation?
Will it have any impact on the architecture?

[gterzian]

Is the idea to

I don't know. I think it is rather about specifying some core things, like a package format, and then to re-use, and integrate with, other specs to described how a "mini-app" could be implemented, similar to how PWA is also re-using other specs.

Will it have any impact on the architecture?

Those are all good question to bring, and to which I have no answer. Regarding separating our components and only compiling what you use, there is also an ongoing discussion in zulip named Improving configurability in servo.

[gterzian]

@nicoburns I remember at the last meeting you mentioned something that "if we did X, the entire Rust community would want to embed Servo as a UI toolkit". Is that correct, and if so, what is X?

[nicoburns]

Make Servo embeddable in an application that is rendered using wgpu (or more generally vulkan/metal/dx12).

I suspect the best solution to this is using child windows and having the system compositor compose the results together. But direct interop between the underlying graphics API could also work.

[gterzian]

Thanks for the info, I have added it above as an "idea" to be tracked in the embedding meetings.

[EemCup]

JSI for Integrate JS engine：
Currently, Spidermonkey is more coupled with servo.
We want to integrate V8 to servo and isolate different JS engines by defining a JSI layer.

[gterzian]

JSI for Integrate JS engine

Added above under "modular script execution"

[Taym95]

JSI for Integrate JS engine： Currently, Spidermonkey is more coupled with servo. We want to integrate V8 to servo and isolate different JS engines by defining a JSI layer.

We can look at react-native JSI and try to inspire from it to create our own JSI.

[gterzian]

Also to track rust-windowing/winit#3506

[gterzian]

Thank you all for attending, next meeting at #120