Re: [fetch] Deprecate fetch (#28)

It's shipped only to ServiceWorkers and behind the flag in the stable releases, according to this page: http://caniuse.com/#search=fetch

Here is for example my first filled issue about aborting problem with ```fetch``` https://www.w3.org/Bugs/Public/show_bug.cgi?id=27841 it's dated by 2015-01-16, almost 3 months from now. I believe there was not much promotion about it in those 10 months and not enough now. So I do not see here or in #27 web-devs arguing what ```fetch``` is very good.

> In any event, there's many platform APIs that return promises where we might want to cancel the underlying activity. This is not novel.

This only means what not only ```fetch``` has problems and what not all should be built around Promises, at least while there is not good solution for canceling them. And best solution of course is to not use Promises. 

As you may notice, we all who are against ```fetch``` with Promises trying to solve cancellation problem. There are few good proposals by @WebReflection and even one by myself. We can live with ```fetch``` and cancelable Promises, as far as they will be cancelable. But this all seems what you are planning to ignore all things proposed by different people and again decide all off-line.

One more thing -- Promises nature is not about cancelation in general and by shipping more-and-more API with Promises which should be cancellable you are doing same mistake again-and-again. It's not too late for ES7 to not use Promises as a basis for ```async```/```await``` since Promies does not fill all the requirements.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/28#issuecomment-89357918