[aseipp]

Not really. Small studios don't even bother writing their own rendering path most of the time; they're using alternative engines (Unity) or middleware (SDL, bgfx/libgdx/webgpu/whatever) to solve the problem entirely because they have better problems to actually slove.

Honestly the real issue is you probably wouldn't get many users or make a whole ton of money, really. Unless you target iOS or iPads, but that can add some significant constraints to the game. (But sometimes it's OK; Divinity Original Sin 2 basically works fine on an M1 Mac or an M1 iPad, as long as you have a Xbox controller to go with it.)

I think as programmers we desperately want to believe it's just a matter of programming and that we're in the critical path here, but it really isn't. Most of that stuff is a solved for a lot of cases. And if it was technological constraints, honestly, there's like a whole host of actual technological concerns, all of them really boring and crappy and not "cool" like rendering (like how do you CI and QA the damn thing, what kind of impacts might it have on your build system, do all the 3rd party things you have work here, etc.) Rendering is just "cool" to talk about but it's not actually as important as those; by the same token you never see giant threads on here about like OS-specific sound APIs or whatever...

There just aren't many Mac gamers and the hardware is kind of expensive to buy and test on for most purposes in that case.