That's literally what I'm now doing for Safari, though. There are very, very few things that don't work automatically across Firefox and Chrome/Chromium/Edgium, but quite a lot where Safari wants it differently. Having to type 'apple' (apple-touch-icon) or 'webkit' (-webkit-text-fill-color) literally into your code is a bad thing in my opinion.
I'm just gonna comment on this instead of everyone and I won't reply after this because I've said my part.
In my opinion this is not comparable at all, slightly differently or prefixed property/attribute names are really very acceptable to me compared to the hacks we used to implement. Having to hack for multiple IEs while also ensuring those hacks are not applied to other browsers was a special kind of evil to battle, and we are not just talking about "oh IE does not support this so we need to do this another way" but also things like "oh IE like to double the specified padding because why not" - and then at some point they removed conditional comments because they were like "IE is good now." which of course it wasn't.
I develop for Safari amongst other browsers daily and have for years, and do not share these frustration everyone else seems to have for it. Do I agree there should be more frequent updates of Safari (also for older MacOS)? Yes. Do I agree iOS should allow other browser engines? Yes. Is supporting older Chromium engines annoying too? Yeah of course, I've run into that as well (don't have any concrete examples right now unfortunately). People like to think that you can expect Chrome to always be the latest version because of the auto updating, but I have experienced multiple issues caused by users with a (very) outdated version. Whether or not you support these depends on your business / target audience, I had to, and it was frustrating.
Different browser engines will always be different and implement standards at different rates, and standards are often implemented before they are finalised and some do this with prefixes and others do not. Supporting multiple browsers is part of the job, if you don't like it you should not be doing front-end web development.
I for one would hate living in a world that is run by Google (Chromium).
