<story><title>Servo’s new home</title><url>https://blog.servo.org/2020/11/17/servo-home/</url></story><parent_chain><item><author>simias</author><text>What&amp;#x27;s the plan exactly? Will there be a Servo browser that integrates the servo rendering engine with some open source components (for instance from Firefox, WebKit or Chromium) that will let us use the engine stand-alone, or is it &amp;quot;just&amp;quot; going to be an engine for embedding in third-party programs?&lt;p&gt;The former seems like it would be a huge amount of work, but if it&amp;#x27;s the latter I fear for the long term survival of the project because it&amp;#x27;s going to be hard to build a community around such a project IMO.&lt;p&gt;Or is there a possibility that Firefox will try to integrate Servo even if it&amp;#x27;s developed outside of Mozilla? Seems unlikely to me.</text></item><item><author>lastontheboat</author><text>We&amp;#x27;ve been cagey about this over the months since the Servo team at Mozilla was disbanded, since there were various moving pieces that needed to fall into place. We&amp;#x27;re excited about the possibility for Servo to continue growing and evolving in its new home, though!</text></item></parent_chain><comment><author>nvrspyx</author><text>A third-option that I would like to see is extending the latter to an Electron alternative (aka using Servo as a cross-platform GUI). There&amp;#x27;s definitely positives to Electron, but it would be nice to see a more performant, less memory hungry, and more battery friendly alternative.</text></comment>
<story><title>Servo’s new home</title><url>https://blog.servo.org/2020/11/17/servo-home/</url></story><parent_chain><item><author>simias</author><text>What&amp;#x27;s the plan exactly? Will there be a Servo browser that integrates the servo rendering engine with some open source components (for instance from Firefox, WebKit or Chromium) that will let us use the engine stand-alone, or is it &amp;quot;just&amp;quot; going to be an engine for embedding in third-party programs?&lt;p&gt;The former seems like it would be a huge amount of work, but if it&amp;#x27;s the latter I fear for the long term survival of the project because it&amp;#x27;s going to be hard to build a community around such a project IMO.&lt;p&gt;Or is there a possibility that Firefox will try to integrate Servo even if it&amp;#x27;s developed outside of Mozilla? Seems unlikely to me.</text></item><item><author>lastontheboat</author><text>We&amp;#x27;ve been cagey about this over the months since the Servo team at Mozilla was disbanded, since there were various moving pieces that needed to fall into place. We&amp;#x27;re excited about the possibility for Servo to continue growing and evolving in its new home, though!</text></item></parent_chain><comment><author>throwaway894345</author><text>With respect to the latter, I agree that it seems unlikely that the project would attract users. Maybe it’s my own ignorance, but I don’t know what kind of apps (besides web browsers) would want just the web rendering engine and not various other components in a web browser. What are the responsibilities of a “web rendering engine” anyway? How tightly coupled is it to the DOM? Does it “own” the DOM, or is that owned by some other component in the browser? In the latter case, how are the relevant aspects of the DOM communicated to servo? And does the rest of the web engine query servo for things (e.g., “what are the exact coordinates of this &amp;lt;div&amp;gt;?”)? If this engine ends up not being so web-specific, then maybe it could be used as a replacement for Skia, more or less.</text></comment>