Excuse me. If it's on MDN, I'm going to use it if it's useful for my app. Not my fault if not all browsers can keep up!
Half JK. If I get user complaints I'll patch them for other browsers but I'm only one person so it's hard and I rely on user feedback. (Submit bug reports y'all)
The issue is completely different if the users of an app or a website are customers. Then you have to make it work for them or you'll lose sales. If it's non-commercial project then it doesn't matter if it works with all browsers or not.
I mostly do stick to baseline widely available, but once in awhile something can only be done with a niche API unless perhaps I include a 10 MiB, slow, clunky polyfill. And for a hobby site without paying users, I basically just don't care.
Can you name some examples? Are those APIs required for core functionality of your websites or are they limited to features that could be made optional?
