Re:Servo announces grant from the NLnet Foundation
by capableweb on Thursday November 09, 2023 @09:15AM
(#38205240)
> 1) there's probably a niche to be filled by an OSS browser engine focussed on embedability
Absolutely. Electron or something Electron-like with Servo embedded could be a nice outcome. Tauri already fills that niche a bit, but uses whatever the OS provides, rather than embedding anything. Would be nice with something in-between that.
Re:Servo announces grant from the NLnet Foundation
by the_duke on Thursday November 09, 2023 @09:20AM
(#38205312)
Tauri is actually adding experimental Servo support.
Re:Servo announces grant from the NLnet Foundation
by capableweb on Thursday November 09, 2023 @11:03AM
(#38206709)
Oh wow, I wasn't aware of this! So proper embedded cross-platform engine into the final binary? That'd be awesome.
Re:Servo announces grant from the NLnet Foundation
by igrunert on Thursday November 09, 2023 @11:49AM
(#38207417)
Yep, embedding the Servo engine into the final binary. This work is sponsored by another (separate) NLnet grant:
Re:Servo announces grant from the NLnet Foundation
by Vespasian on Thursday November 09, 2023 @09:01AM
(#38205071)
Wild speculation: With iphones being forced to open their web engine there might be some apps interested in embedding their own engines across mobile devices.
Re:Servo announces grant from the NLnet Foundation
by paulrouget on Thursday November 09, 2023 @10:44AM
(#38206437)
> My personal hope is they push hard on the modularity angle
It is strongly designed that way (the component model and the embed layer).
Re:Servo announces grant from the NLnet Foundation
by wongarsu on Thursday November 09, 2023 @11:25AM
(#38207102)
An embedded engine is also a much faster path to viable use cases. For example Sciter [1] has some degree of success despite implementing only a sane subset of the DOM API. It doesn't work well for general internet surfing, but when used as an UI library you just avoid the parts that don't work.
My personal hope is they push hard on the modularity angle. Seems to me that:
1) there's probably a niche to be filled by an OSS browser engine focussed on embedability
and
2) That it could be a huge boon for the long-term health of the web platform if there are build-your-own-browser "lego building block" libraries that people can mix and match to create new engines.