I work in games for a fully remote company. a Mac mini takes ~5 hours to compile and cook (read: prep the assets) for our game. It's not reasonable to ask someone to have that mac at home, and even if it was, you have to have it somewhere where it's available, has high speed internet, and that person is responsible for the hardware - making sure it stays on when it's needed etc. That person also needs to deal with any hardware failures/ warranty replacements. Instead, we could lease a mac from AWS for £20 for a day, run a build and use that.

That doesn't mean that this is a scalable solution for running our business on, but for the occasional one off mac build to make sure it's not fallen behind, it works just fine for us.

First world problems.

In some other countries I have seen an iMac been shared across teams that would take turns at the device.

In Germany I would state the same statement, we live between Windows and macOS on the office, but I also have some care for those that aren't so lucky.

Geez yeah if I was making roughly $1k USD every three days I would definitely be a Mac guy, no question.

Not a better use of time to get them implemented?

In this case I meant taking an approach similar to this one for bazel[0] that is not limited to only code that works on Linux. It would only allow you to build on Linux and would require any testing / running would still happen on macOS, but that might still be worth it in some cases. Theoretically you could deploy your iOS app that way as well.

[0]: https://github.com/apple-cross-toolchain/rules_applecross