As someone who has worked in quite a lot of web projects for the last few years I noticed the big difference in requirements. Back when I started it was all ab

As someone who has worked in quite a lot of web projects for the last few years I noticed the big difference in requirements. Back when I started it was all about supporting IE7/IE8+, Firefox, Opera, Chrome and Safari (with an old iPad as a test device). A lot of polyfills were used to ease development and keeping older browsers alive. Testing on IE was quite painful (missing proper devtools, weird "Unknown Error!" alerts, slow scripts crashing the whole browser, browser implementation bugs, headaches with library conflicts, etc). I remember testing against hobby browsers like Pale Moon because things already worked fine. Nowadays it's just all about testing in Chrome and with less priority, Safari (mostly on iPad, iPhone). The requirement of testing against other browsers were dropped by most of clients. If a project has spare time fixes for those browsers are an extra. Most analytics tools don't even show anything else of Chrome/Chromiums and Safaris (desktop and mobile). So, even older engineers are slowly moving along with the newest generation and just test on Chrome and sometimes Safari. This days I just use a Chromium derivative, Vivaldi. It does the job and the UI speed has been improving quite a lot (but still lags a bit behind). If the project has some spare time I like to do some cross browser checks (most times, things just work fine). Sometimes I find an engineer using Firefox but most of the time they have a Chrome browser opened to test their work.