I heard (from the horse's mouth) that the entire Servo team has been "acquired" by Mixed Reality. Reams and reams of Internets back and forth make it clear that this is actually what happened and not a miscommunication of some kind. https://blog.servo.org/2018/03/09/servo-and-mixed-reality/ …
-
-
Replying to @wycats @asadotzler and
"if we can make it work for VR, it'll be great for desktop web" has a kernel of truth, but was mostly a messaging dodge. Servo is deprioritizing finishing web compat in favor of MR.
2 replies 1 retweet 1 like -
Replying to @wycats @fabricedesre and
I'm just one person, but the way I see Servo is as R&D for things that might make it into Gecko, delivered to users in a Firefox browser. That work continues. What may not continue is turning Servo from an R&D engine into a commercially viable full web platform implementation.
1 reply 0 retweets 0 likes -
Replying to @asadotzler @fabricedesre and
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.
1 reply 0 retweets 0 likes -
Replying to @wycats @fabricedesre and
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."
2 replies 0 retweets 0 likes -
Replying to @asadotzler @wycats and
WebRender in particular is on the top of the FF roadmap for performance improvements...
1 reply 0 retweets 3 likes -
Replying to @aaron_turon @asadotzler and
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.2 replies 0 retweets 3 likes -
Replying to @aaron_turon @asadotzler and
TLDR a full servo browser is very far off and needs lots of webcompat work. If we focus on the portions needed for a decent VR browser, we're still making progress here.
2 replies 0 retweets 1 like -
Replying to @ManishEarth @aaron_turon and
Additionally the portions needed for VR are quite overlapping with what's needed for a ServoView or Servo-Electron-thing -- support most web things but not weird quirks. Make it feasible to target specifically, basically.
3 replies 0 retweets 1 like -
Replying to @ManishEarth @aaron_turon and
Jumping in here, but - oh my god yes please "servo-electron". Don't even need float/tables/etc, prob any legacy css. Don't even need any embedded media or lots of other web stuff. Allow me ship a <50MB app and you're a serious contender
2 replies 0 retweets 4 likes
Flexbox-only block layout would work fine for this use-case. ReactNative proves that.
-
-
Replying to @wycats @ManishEarth and
For the most part, yes. I still drop down into `display: block` for pieces of content, like modals, that have paragraphs and other inline content. But most of the app is all flexbox.
1 reply 0 retweets 0 likes -
Replying to @jlongster @ManishEarth and
Yeah, I think people underestimate 'content' (it's why web views are so popular in native apps) but I think you could get away with a small subset of the block content spec for these use cases.
0 replies 0 retweets 2 likes
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.