10 STYLING
20 LAYOUT
30 PAINTING
40 GOTO 10
At styling and layout I use dirty flag managment, so that branches of the component tree is restyled or layed out only if needed. This kind of dirty-management makes stuff a bit more complicated than otherwise, but this is a tradeoff. At painting I did not implement caching (painting to a memory buffer) and dirty flag management yet, but here I will also do optimizations in the future. This is a bit tricky, as painted components can have alpha/trasparency.
The most serious bottleneck will be probably painting (everything else can be addressed with algorithmic optimizations). At the beginning of the project I've looked at canvas painting benchmarks, and I decided canvas performance is already quite good. The slowest is drawing texts, but even that is not that terribly slow. I expect that canvas performance will improve in the browsers in the future so time works for me. Currently my samples' performance feels acceptable, although I did not do serious performance tests yet (and as I mentioned I did not implement the most agressive optimizations regarding painting yet.)
TL;DR: Making this fast is quite challenging, but not undoable I think.
To go further I will certainly need outside help (either other programmers or funding or third party component creators). I cannot create a huge component lib myself. But 10 people can do lots of things I think.
http://blogs.gnome.org/alexl/2011/03/15/gtk-html-backend-upd...
I am doing it in my free time (at nights), because I have no funding: it is a quite huge undertaking: I am ready with 5300 lines of code, but I still need a couple of weeks just to release a very early demo. My secret aim is to make it a flash/flex killer in the long term. In the very long term:)