I don’t personally really see much value in having a bunch of different browser ‘skins’ that all use the same underlying rendering engine. There’s not much room for innovation there.
It’s great that Blink is open source, but I’m not sure how open source and malleable the road-map is compared to e.g. Gecko. Generally web features and standard are implemented/proposed because Google has an interest in them. This often overlaps with things that other developers have an interest in too, but not always. Sometimes implementing such features has unintended consequences.
Not Trident - but generally yeah, at work it’s normally a case of supporting EdgeHTML (Edge), Blink (Chrome), Gecko (Firefox) and also WebKit (Safari). These are tested via BrowserStack if not available natively (Safari on Mac).
Safari and Edge are usually the two most annoying browsers to try and support, with Safari the biggest pain (iFrame sizing is awful, and it lags well behind on newer web features like
WebAssembly.instantiateStreaming). I don’t think I’d be doing my job properly if I just ignored them and didn’t make an effort, though. Maybe if you’re publishing an Electron app you can justify not bothering cross-browser testing but if you’re releasing a web app it’s poor.
I’ve dealt with enough apps that generally leave my platform (Firefox/Linux) out in the cold to be frustrated by this. For a long time, Google never bothered supporting Hangouts/Allo for Web/Google Meet/Google Earth/YouTube TV on Firefox. Netflix still serves me degraded quality content despite paying for a 4k plan. It’s not like the web platform features were missing for a lot of those either, I can only assume it was laziness.