Let’s face the fact – browser wars are still ON! I think it is on a different dimensional time/space coordinate these days – consumers really don’t care anymore, “My device [substitute: tablet, phone, thermostat, etc.] has an app that works; what’s wrong with your site/service?” they rant! So who cares then? Developers.
The point is, the consumer (developers seem to forget they too are consumers) does have an “app for that” and it most likely uses the underlying browser technology installed on their device. So we developers are thus obliged to DWI.
We cannot control it. We cannot change it. We can only barely influence a small segment of it.
In my opinion developers are worse than the general population when it comes to complaining about perceived incomplete features. I don’t know, but maybe we developers are just built that way. We will call Microsoft by all sorts of names that really should not be used around children, when they release new “incremental” builds, leaving out the very thing, the very API that will solve all our immediate issues on our current punch list.
I don’t know Jake but he acknowledges the same sentiment:
Bit of a rant: it bothers me that as developers, we preach iterative development and release, but when we’re the customers of that approach the reaction is all too often “HOW DARE YOU PRESENT ME WITH SUCH INCOMPLETE IMPERFECTION”.
Maybe DWI is a good plan for long-term business success. Yep, it is a business expense to DWI when DWI = change. It is also a business expense to loose a customer. Customers like voters will tolerate a problem for a while. When tolerance runs out, its like Crosby Stills Nash and Young song title form way back, they’re: “Long Time Gone”. Your customer could be “Long Time Gone” too, if you don’t DWI – timely.
fetch(… Browsers are mini-operating systems. More and more the browser is being integrated deeply into work-flows – at very low levels, just like an operating system call. As this happens there will be no other choice in implementations. The developer will suddenly find the choices have already been made. While I wasn’t looking browsers changed. I am “re-thinking” a lot of my current code development practices. I am as Captain Picard (Star Trek TNG in Darmok episode) was in the closing scene: Darmok, His eyes wide open.