When you used a built-in interactive HTML UI component (e.g. textarea, select, checkbox) in the browser was it because? A) Accessibility?
B) A better polished/integrated user experience than any JS library provides. C) Meh I just needed to throw something together.
-
-
Honestly, our experience with Service Workers has been very disappointing. It still has so much overhead that negates the effectiveness. Also, still difficult to truly take advantage of long lived large caches across websites to build user space tooling. :(
-
Can't have it both ways. As you said, the initial implementation of a secure user exposed primitive like this is gonna be slow. But having network and Cache exposed is a genuinely good start and massively better foundation than app cache.
-
If you consider being on the right track as a success story, sure. I'll hold my claim of success until it is also fast and can successfully start large code bases from cache immediately.
End of conversation
New conversation -
-
-
In the meantime, browser vendors have reminded themselves that they really do want declarative syntax so they can do optimizations, which is a short-sighted analysis but one that they've been shouting ever loudly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.