The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Raising head to be shot.
Dont hate on <insert noun=""> without first knowing the constraints they had.
Blame the company all you want for being lazy but not the workers unless you have a tad more data points to say they had enough resource to be developing for more then IE. If site was built in last 2 years, yes.
Sites for cookers, which yours sounds like, could be template site from 10+ years ago.
We are living in the age of software architecture-by-middle-level-managers: "Use this (software) tool, it's hot; be done by Friday (or else)." This is where all our technical debt came from.
So, are programmers lazy? If you include being forced into hastily written code by higher-ups as lazy, then yes. Whichever is the case, their software output is indeed eating the world.
My list of web sites that FireFox cannot handle is growing steadily. Sometimes, the entire page won't display. Sometimes, most of it works, but links to external resources (such as videos or discussion fora) are not handled. Some hooks that used to work with FireFox (e.g. for picking up the URLs of videos I view in FF), but a year or two ago, they changed something that forces me to switch to another browser.
I try to avoid anything that has the "Google" stamp on it (in particular if there is any sort of login) - they are just too clever at invading my privacy. So my backup browser currently is IE11. FireFox does handle a few things well, though: E.g. I like the history mechanism. So for now, I still stick to FF as my first try, and go to IE11 only when FF fails. That happens more and more frequently. Every new FF release seems to add more websites to my "Doesn't work with FF" list.
I do not have the spare time to get involved in FF development. Whatever is claimed: Reporting "problem websites" to the developers so that they can look into it never has any effect. I used to do that earlier, both for commercial and open source project: It never lead to anything. Usually, when I check two years later if anything has changed, the problem is still as strong and lively as ever.
So there are strong hints that I quite soon will have to find myself another default browser. It won't be Chrome. An alternative that is both Google and MS is not quite among my favorites. So maybe I will switch to IE11 as my default, not only when having problems, and then go to FF for those pages that doesn't work with IE11.
Now the world has gone to bed,
Darkness won't engulf my head,
I can see by infra-red,
How I hate the night,
Now I lay me down to sleep,
Try to count electric sheep,
Sweet dream wishes you can keep,
How I hate the night.