> If it's not broken why do so many devs refuse to support it because things they code in Chrome don't work in it.
You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox.
Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities.
I was doing front end dev in the IE6/5.5 era so yeah it’s incredibly frustrating to hear it over and over when you’re right deep down it’s all excuses because supporting one browser is less effort.
You'll surely meet a lot of people doing what you mention. I would bet most of them are young enough to not have gone through the so-called "browser wars" [1], at least what they now call the first one, the one that ultimately led to the creation of Firefox.
Their attitude does not mean at all that there's something actually broken in Firefox, just that it is so much easier -and lazier- supporting a single browser's quirks and ignoring the rest. Even if that means discarding standards and compatibility. Specially if it means that, because you will take advantage of those particularities.
[1] https://en.wikipedia.org/wiki/Browser_wars