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

> I think it would be good to leave it.

I do also.

> For every 1 developer who gets outraged and believes that their use case is truly unsolvable without janking the user experience, and comes to complain here, there may be 10 or 100 more who see the message and improve their user's experience, and alongside it the health of the web ecosystem.

Yes. Speaking from my perspective in development of messages for the HTML checker, and seeing the results, I know messages about deprecated-but-still-supported misfeatures can make a difference during the time while browsers have to  continue to support them and we continue to be stuck with them until more developers learn how bad they are for users and quit using them.

So in the interim, such messages have the potential to eventually reduce the usage to the point where we can actually remove the misfeature.

In this case I realize the odds might seem long right now, and the usage may end up remaining high enough forever that we never actually get there—but if we just give up on doing things like continuing to raise developer awareness of the problem by emitting console messages, we’ll never know if we might have been able to reduce usage below the threshold.

---
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-198852554