Re: Last Call comments

> Sure, but let's avoid obvious hyperboles. You said EVERY, I didn't say none.
>> In second, any errors in this code will be repeated hundreds of times.
> Are you saying that it will by copy-pastd hundreds of times and the original source won't be used? If the actual source is used, then the fix is also deployed to all sites easily.
>> In third, "not so many developers need to write the same code" doesn't answer the question why we are forcing to write such code at all.
> No, it doesn't. But you continue to ignore the answer which is that many developers want it.
>>> Also, what's wrong with iteration? Why is it imperative that v1 contain everything?
>> Then between first and second iteration hundreds of developers will write thousands lines of code which will be thrown away at the V2 spec release.
> Please stop with the hyperbole. There won't be hundreds of developers writing thousands of lines of code. All of jQuery core is only thousands of lines of code. All of hammer.js is 1,217 SLOC. So realistically, we're talking about a handful of developers writing a few hundred lines of code.
>> Maybe we should answer then why to release v1 spec if it obviously lacks the mechanisms which are needed by every developer?
> Because it's clearly not needed by every developer. Not even close.

Okay, I'm hyperbolizing, most probably. But, for example: how many times developers wrote (or copy-pasted) the code to work with XMLHttpRequest? Something like that:

var xmlhttp = new XMLHttpRequest();'GET', '/xhr/test.html', true);
xmlhttp.onreadystatechange = function() {
  if (xmlhttp.readyState == 4) {
     if(xmlhttp.status == 200) {

I saw it many times, though every popular framework provide its own implementation. I think there are literally thousands of copies of this code on the different websites. The code snippets for pointer counting and pointer dispatching will be copy-pasted all over the web just like this one.
And you may note that this snippet is bad: it doesn't contain error handling, for example. Exactly the same thing will occur to the PointerEvents code snippets.

The current spec doesn't cover basic PointerEvents use-cases, and that's why I found it unsatisfactory.

Konstantinov Sergey
Yandex Maps API Development Team Lead

Received on Wednesday, 10 April 2013 10:13:46 UTC