Aiosa

> When you say it takes a little longer at startup, how much longer are we talking about? With cached tiles in browser, the synchronous loading happens instantly. With the...

> Yeah, I think we should assume we're getting rid of (deprecating for now) tile-drawing. I did not want to deprecate this event. For the canvas drawer, it is still...

:) I want to support events, since these enable effortless plugin interaction. With WebGL, I want to promote shader modular compilation, since that's what will be the most performant, but...

Actually, if the event was async we _know_ when updates have finished so that we can collect requests for redraw, how many times the main tile cache was touched, and...

@iangilman you were right, I take it back, `tile-drawing` should be deprecated. It is supported only in a single drawer as of now, and there is `tile-drawn` event I did...

The problem is that you don't want to remove the tile from the system nor fire `tile-loaded` event - users might have custom caches, they need the freedom to decide...

Thanks for the fresh view, I will try to comment on thing that are different in the current implementation or things I view differently or just want to add explanation...

Ok, if we do some nice hacking on the `add-item` event, the cache initial loading is also fast. We could play with heuristics to make the initial load boosted, or...

I solved this like this: // do something to start the test cy.visit({ url: ..., headers: ..., method: ..., body: ... }) // custom function utils.waitForViewer(); you can check the...

I leave it here as a docs for later, RN I have no cappacity to fix this.