Re:Version 100 in Chrome and Firefox
by Uehreka on Tuesday February 15, 2022 @03:24PM
(#30352132)
I feel like these arguments always break down along the same lines:
- People who have recently run into an issue that required browser sniffing
- People who haven’t and feel sure that “things are better now” and the practice is no longer needed.
I’ve gotten into these kinds of scrapes many times, and I can assure you all that philosophical arguments about browser-detection-vs-feature-detection don’t work very well when you’re trying to explain to a client why their web app that worked a week ago doesn’t work today (due to a WebRTC bug in Chrome, for instance) and won’t be fixed until the next Chrome version comes out in six weeks.
To folks advocating “ripping off the bandage” as a solution, I’d note that the wound underneath has not stopped bleeding.
- People who have recently run into an issue that required browser sniffing
- People who haven’t and feel sure that “things are better now” and the practice is no longer needed.
I’ve gotten into these kinds of scrapes many times, and I can assure you all that philosophical arguments about browser-detection-vs-feature-detection don’t work very well when you’re trying to explain to a client why their web app that worked a week ago doesn’t work today (due to a WebRTC bug in Chrome, for instance) and won’t be fixed until the next Chrome version comes out in six weeks.
To folks advocating “ripping off the bandage” as a solution, I’d note that the wound underneath has not stopped bleeding.