Earlier quoted context omitted.
You don't need a windows build server to build a windows app, its just an executable that targets a given cpu architecture or run-time. Its not about affording a Mac Mini its about being forced to do IT on some build servers when the rest are visualised in the cloud. Having your cloud servers ping back into your physical office to do the Mac build is stupid. For context, this is an online service where we wanted to b…
You don't need a windows build server to build a windows app, its just an executable that targets a given cpu architecture or run-time. Have you tried building a native or .Net Framework app on a Linux machine? How did that work out? Its not about affording a Mac Mini its about being forced to do IT on some build servers when the rest are visualised in the cloud. Having your cloud servers ping back into your physical…
Well now we have .NET core so its fine but previously one can C, one can C++. Its not always ideal but there are options.
This issue is that if my highly public office with full glass windows in a somewhat shady part of town gets a power cut or broken into then I've got to run around to find another mac. Even if the network goes down I have issues that happen WAY less on the cloud. Its annoying.
What's more annoying is that there's no solid technical justification as to why this is. They just want Apple hardware to sign their builds because they want you to buy Apple hardware.