What it has been: a pipeline for risky web platform experiments that can make their web back into Gecko to make Gecko better. I don't particularly see any reason why good Gecko engineers couldn't take some time away from the grind to prototype ideas.
The sudden shift in prioritization from web compat to VR projects described in the post (https://blog.servo.org/2018/03/09/servo-and-mixed-reality/ …) belies that. "Just not a full fledged product" is the party line, not a reflection of the the technical and organizational decisions that were made by leadership.
-
-
And I point you again at https://github.com/servo/webrender/issues/2506 … the horse's mouth as it were. "we're still planning to continue to both have the Mozilla Servo staff work on Webrender and Pathfinder and the Firefox team investigate its use inside of that product."
-
WebRender in particular is on the top of the FF roadmap for performance improvements...
-
But the ongoing work to reach full production quality is happening within the FF team, while Servo folks press on to things like Pathfinder. Webcompat work on parallel layout is ongoing and is needed for MR. just talked with
@ManishEarth about that this week. -
Will the integrated Gecko version be used/usable by Servo?
-
Patrick is still full time of Pathfinder. The plan is to integrate Pathfinder as a part of WebRender. Both Firefox and Servo use the exact same WebRender repository.
-
My main hope is that Servo doesn't get behind Gecko on web compat when its own components get integrated with Gecko, because that would make future experiments in Servo harder. But this really isn't about Servo. Really sorry Servo got dragged into this.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.