3 ms·

I appreciate what you're trying to say there, but in practice most developers can't adopt this solution. Unless you're writing for known platforms (an internal

I appreciate what you're trying to say there, but in practice most developers can't adopt this solution. Unless you're writing for known platforms (an internal web app, say) or building a throwaway demo, you will practically speaking have to compromise and support vendor-specific code where it's required by your users. The goal of most real-world software is to deliver a working, usable product – not to produce lots of standards-compliant code.

gaelow 12y ago
The goal is to deliver the most profitable code in the specified timeframe and with the resources provided. That's how you organize your priorities. For us in many cases it means to throw away vendor specific solutions in favor of most-major-browser compatible subsets of the current industry standards, even if it means throwing out support for older versions of IE. For some users it might mean using a different service, but for most of them it means switching to a different browser because their favorite app doesn't work on IE. And that's why Microsoft is going for standards compliance and timely browser updates more than ever.