> Are you saying that you’re ready to put your name on an app you’ve shipped but never tested yourself?

At work, I do this for in-house command-line tools. I have automated unit tests and integration tests, and all the compilation is done on a CI server. And if a problem slips through automated testing, well, then somebody will ping me on Slack and I'll fix it.

I only need to take out my MacBook Air to debug something once every year or two.

We may actually need to start a conversation at work about whether we want to continue supporting Macs internally. We could notarize our own CLI tools, but we also rely on lots of open source CLI tools, and I understand that all of those will eventually need to be notarized, too.

In poorer countries many Devs might not be able to afford the newest $800 iPhone for their potential career start.

I’ve had users who requested a mac version of a tool I develop and provided testing for it.

I can’t test on a mac, as I don’t have the money for one, so I build the binaries with Travis CI automatically, and never test them myself — I also can’t notarize them, obviously.

let's say you're an open source app, and develop on linux using electron. there are some people that would like to run your app on a mac, but you don't have one. you can set up github CI so that your app gets built into an appimage, that's a little work, but not much. should you now also be required to pay for the luxury of sending one or two people an app? should they pay for it?

this is not hypothetical; I literally just received a GH issue update asking if we can use community funds for the $100 ransom^Wfee.