Re: [dev-servo] Meeting notes 3/16 (Android nightlies; Q2 focus; testing strategies; usability; layout direction; Rust upgrade blocked)

Sure, I agree that if you're doing custom layout languages (Cassowary, etc.) Houdini is a win—the comment was more directed toward use of Houdini to reimplement layouts that can already be described with CSS. For those use cases, without seeing any numbers, I'm unconvinced of the performance

Re: [dev-servo] Meeting notes 3/16 (Android nightlies; Q2 focus; testing strategies; usability; layout direction; Rust upgrade blocked)

I have concerns about implementing full CSS algorithms in JS. People seem to think that makes it fast by default. It's more that what people are currently doing is crazy slow. Namely, to implement a custom layout today, you typically have to a) identify some DOM elements to measure (typically

Re: [dev-servo] Meeting notes 3/16 (Android nightlies; Q2 focus; testing strategies; usability; layout direction; Rust upgrade blocked)

On Tue, Mar 17, 2015 at 3:12 PM, Patrick Walton pwal...@mozilla.com wrote: Sure, I agree that if you're doing custom layout languages (Cassowary, etc.) Houdini is a win—the comment was more directed toward use of Houdini to reimplement layouts that can already be described with CSS. For those