- From: Jason Stewart <notifications@github.com>
- Date: Tue, 22 Mar 2016 22:43:03 -0700
- To: whatwg/xhr <xhr@noreply.github.com>
- Message-ID: <whatwg/xhr/issues/20/200192088@github.com>
With enough time and effort, yeah, I can program around this, but I have many customers with many different systems. If one day they all upgrade their browsers, and sync XHR stops working, that's not a good day! Lots of billable hours? Yes. Billable hours that I want? No. I'm having a hard time understanding the value-system that gives priority to a cosmetic concern (which can be self-remedied) over not-breaking existing code. Look at how many terminal-based applications that we use as developers. As a platform, the terminal lacks a great many things, yet it is _stable_, which lets the developer focus on the problem instead of the platform. When you have a platform that makes changes lightly (windows, gnome, android, iOS, etc.), instead of being able to double-down on the quality and functionality of your program, you end up in a perpetual struggle to keep your app functioning correctly across all of the different versions of the platform. It's stagnation. It's IE all over again. --- 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-200192088
Received on Wednesday, 23 March 2016 05:44:03 UTC