&gt; That&#x27;s not what I&#x27;m asking for. You&#x27;re pointing to low-level metrics and I&#x27;m asking for high-level examples of things not achievable today that Servo will enable.<p>I don&#x27;t think there are many such things as stated, because the Web is technically capable of almost anything you want to do already. Even if we were to say that CSS is too slow to do the things you need to do (which I don&#x27;t believe at all), you could always do the famo.us thing, rebuild your interface in WebGL (and even maybe throw out JS in favor of asm.js), and do anything you might possibly want to do in existing engines.<p>What I think Servo will do is to make it <i>easy</i> to make Web apps fast, by eliminating the huge distinction between the slow paths and the fast paths. In my view this is the biggest performance win we can possibly get on the Web.<p>To be sure, I&#x27;m not saying that Web developers are bad and that it&#x27;s their fault :) The browsers have created this situation, after all. It&#x27;s not that the Web is incapable of being fast. It&#x27;s just performance on the Web is a minefield. I think the biggest thing Servo can do is to eliminate that minefield.