HTML5 update: why it is slow?

[Trevor DeVore]

On Wednesday, January 6, 2016, Monte Goulding <monte at appisle.net> wrote:
>
>
> Personally I’d rather you declare force majeure on wait for HTML5 and
> apply your considerable talents to implementing non-blocking versions of
> everything. Wait et al causes issues all over the place, is usually the
> least efficient way of doing things and the end result is almost always a
> poor user experience. Given the choice of a little bit of extra coding work
> implementing callbacks but with the side benefit that users won’t be
> sitting there wondering what’s going on and an engine that’s either 22x
> faster or half the size (both of which are critical issues for HTML5) what
> do you think people would choose?
>

Amen.

-- 
Trevor DeVore