5 ms·
Surely you'd want CI builds for your app? I suppose you can always go the sassy option and just offload this problem onto Travis or CircleCI, but then they're t
by mikepurvis 6y ago
Surely you'd want CI builds for your app? I suppose you can always go the sassy option and just offload this problem onto Travis or CircleCI, but then they're the ones stuck figuring out how to rack thousands of Mac Minis, dealing with thermals in a machine that isn't set up for hot/cold aisles, a computer that doesn't have a serial port or dedicated management interface, etc.
If you're a big enough org or the app is for internal use, this might not be an option anyway. At that point I imagine most people just give up on it and figure out how to run macOS on a generic VM. But at that point you have to convince your IT department that it's worth it doing a thing that is definitely unsupported and in violation of the TOS.
Or maybe some of these are big enough that they are able to approach Apple and get a special license for N concurrent instances of macOS running on virtualized hardware? Who knows.
- damnyou 6y agoNo company on the planet is big enough for Apple to make exceptions like that. All of them either use a cloud provider or a custom rack design just for Mac Minis.
- IntelMiner 6y agoCompanies like Google or Microsoft aren't big enough? Google's Chrome and Microsoft Office alone I would wager are more than big or popular enough to get special treatment Adobe is smaller by contrast but I'd speculate has a much deeper relationship with Apple as well
- damnyou 6y agoAll of them use Mac Minis as far as I know.
- pjmlp 6y agoNope, just build straight from XCode.
- mikepurvis 6y agoWell sure, for a single person team. But as soon as you're working with other people, surely you want an independent machine making builds and running tests— this is literally item 3 on the Joel Test.