Isn't one of the reasons that a web app won't respond immediately to a button click is because of a built-in delay on the browser level on touch devices? The on

Isn't one of the reasons that a web app won't respond immediately to a button click is because of a built-in delay on the browser level on touch devices? The one in place to allow for some time to know whether the user intended to do a touch event versus a drag event? For instance, I've made a simple tic-tac-toe app that I have on my phone through Phonegap that uses nothing but canvas for rendering. It doesn't seem to have this built-in delay and the buttons are quite responsive. I don't think your example of the carousel works because the article, I believe, was referring to the programmers that are working on the browser itself. You can't necessarily hold them responsible for performance issues derived from what other programmers are doing on the platform that may or may not be a good idea. Besides, I would imagine you could build a rather snappy carousel these days on modern browsers using CSS3 features as the bulk of the animation as they are native to the browser. You are also comparing today's Javascript endeavors to those of native developers that have already had their issues worked out, as you say. It would only be fair to wait until current Javascript issues are worked out before doing a proper comparison. It would be like saying your car is the obvious choice for the race because it outperforms my car even though I've yet to put the tires on my car. Native is the proper choice today, but who knows what tomorrow may bring?