3 ms·

> The problem is that the CSS rendering stack is old and needs to be revamped. I thought that was the point of the 5+ year long flexbox? Are you telling us t

• pcwalton 11y ago
  Flexbox wasn't about performance, and these issues are largely about performance. I think Flexbox pretty much fixed the complaints about the expressiveness of CSS for UIs (unless you're forbidden from using it for browser compatibility concerns, of course).
  • Touche 11y ago
    It certainly wasn't sold as "not about performance". Performance was blamed on things like floats in the past, and flexbox was supposed to solve the needs without sacrificing performance. Now you're saying that CSS needs to be revamped. Great. Anyone working on that? Either way we're looking at, what, 5 years minimum before first browsers have this new thing that's really about performance this time, for real.
    • pcwalton 11y ago
      > It certainly wasn't sold as "not about performance". Performance was blamed on things like floats in the past, and flexbox was supposed to solve the needs without sacrificing performance. That's not true. Do a search for [flexbox floats performance] and you'll see that the goal was not to improve performance of floats. Floats are only a performance problem in parallel implementations, which nobody was talking about at the time flexbox was created. > Now you're saying that CSS needs to be revamped. Great. Anyone working on that? Gotta love HN snark. I work on that every day, 50+ hours a week. And I'm not saying revamp the specs. I'm saying revamp the implementation.