Not quite, I think.<p>I&#x27;ve been using it, it&#x27;s cool and all, solves some common CSS issues, but it comes with its own set of problems. For starters, it&#x27;s a whole new set of browser incompatibilities that you have to learn [1], some of them render flexbox almost useless [2]. Additionally, IMHO, it&#x27;s model is <i>leaky</i>; leaky in the sense that the it relies on DOM structure - a `display: flex` element will do it&#x27;s thing by affecting the direct child elements. This means that a) if your component is wrapped by another component, you&#x27;ll have a hard time predicting how it will be laid out&#x2F;isolating the behavior; and b) if, by some reason (e.g. using Angular directives) a wrapper is added between the `display: flex` and the flex item elements, the layout will be lost.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;philipwalton&#x2F;flexbugs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;philipwalton&#x2F;flexbugs</a><p>[2] <a href="https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=346275" rel="nofollow">https:&#x2F;&#x2F;code.google.com&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=346275</a>