It was never debugged enough to be turned on on desktop, but I think it was considered useful enough to ship on mobile in the days when mobile performance was significantly worse than it is today. In particular, on a network where request latency is high having to pause treebuilding for scripts to download can significantly increase the time until it's possible to paint anything at all on the screen.
That's not to say Servo shouldn't try it of course! Part of having a healthy multi-browser ecosystem is each browser trying lots of ideas and coming up with new solutions to problems that were encountered in other implementations.
[1] http://trac.webkit.org/changeset/162260/webkit (the number cited here is a joke :P)
[2] https://groups.google.com/a/chromium.org/forum/#!topic/loadi... (see also the design doc linked from the email)
WebKit/Blink put fewer parts of the HTML parser off the main thread, so negative results should not be taken to apply to more comprehensive approaches.
> I hope to publish another blog post describing [speculative parsing] thoroughly, along with details on the performance improvements this feature would bring.
Isn't there any preliminary results on the perf improvements this would bring?
I understand that the % of time when the speculative parsing succeeds (instead of having to roll back to a sequential parsing) can't be know easily, since it'll be based on the testing of a large number of real-world web pages,
but I'd love to see just 2 simple examples:
* One full of `document.write`, so we can have an idea of the time lost in case of failed speculation
* One 'embarrassingly parallel' dom tree where the speculation should pay off the most.
That would give us a good idea of worst case / best case results.