3 ms·

To be honest the spec is such a convoluted mess of hacks and patches, I'm amazed it's stuck to at all. At work we actually stopped bothering supporting all brow

To be honest the spec is such a convoluted mess of hacks and patches, I'm amazed it's stuck to at all. At work we actually stopped bothering supporting all browsers for our product because of the endless compatibility issues, and just told our customers to stick to Chrome, which they were fine with. End result is a simplified and streamlined development cycle for us, no time wasted on fixing other browsers, and we always get to use the latest features (Chrome just seems to be up to date with everything straight away). Customers were already using chrome as their default browser anyway, so it's a win win.

munchor 9y ago
We do the same thing (Chrome and Firefox, though) but as an engineer I always can't help but feel terrible because I don't want the "Web" to start meaning "Chrome". It would be terrible for the Web to be totally controlled by Google. I guess it's the other vendors' fault though for not implementing standards as quickly and efficiently enough as Chrome… Also, the fact that Edge can only be ran on Windows means that developers working on Linux or Mac can't (easily anyway) test/adapt their websites for Edge. This is another reason why Edge is usually left behind even though it is pretty up to date with most Web standards.
ddebernardy 9y ago
Back when I was still regularly doing front-end work, anything that would work on mobile safari and on desktop safari would work fine on other browsers. Have things changed that much in the past few years?