Re: [xhr] Abandon hope of removing sync XHR from the web platform? (#20)

The opinion voiced by the WHATWG members here seems to be: "If only we can educate these fools who are still using `async: false`, then usage will drop low enough to where we can remove it!"

No one uses `async: false` by accident.  It is not the default.  No one stumbles into it.  No one **_wants_** to use `async: false`.  Developers use `async: false` because they have been painted into a corner where it becomes the lesser of two evils.  My particular corner involved a 3rd party library that I would rather not fork.  Others' corners seem to involve 3rd party libraries that they **cannot** fork.

The usage is not low because you are spreading the gospel.  The usage is low because, like a lifeboat or a spare tire, you only need `async: false` on a rare occasion.

There would be far less griping over this if one of the proponents took the time to write-up why `async: false` is so evil.  Not just _**slow! unresponsive!**_ [Duh], but an actual, technical, non-insulting article on why this feature is better dead than alive.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/20#issuecomment-198857594