> the day Nvidia releases a driver which implements the required APIs it will work with no changes in my code.
How about the day when Nvidia releases a buggy (system-crashing?) implementation of the required APIs? How well will your code work without changes, and which course of action will you take?
I'll not change my code for their sake. I already get enough annoyed Nvidia users who think it's my fault their driver doesn't support GBM, so annoyed Nvidia users who think it's my fault their driver is buggy won't be much different. I'll do what I already tell them: it's Nvidia's problem, report it to them. Of course, if some characteristic of Nvidia's implementation demonstrates previously-unknown bugs in sway (bugs in sway, not in the driver), sway will change to accomodate that.
Your project, your rules - but that attitude doesn't scale well.
Chromium chooses to prioritize users' experience over scoring ideological points. That means attempting to work around known external bugs instead of letting things blow up and sending users to pound sand on some unresponsive third-party mailing list.
I'm not sure how you can fault them for that, especially since pretty much all successful large-scale projects take the same approach -- including the Linux kernel.
How about the day when Nvidia releases a buggy (system-crashing?) implementation of the required APIs? How well will your code work without changes, and which course of action will you take?