> I am a developer.
Ill bet you 99% of mac sales are NOT to developers.
Despite them arguably wanting to court developers to write swift programs, their hardware sales team doesnt seem to care about developer prosumers.
Ill bet you 99% of mac sales are NOT to developers.
Despite them arguably wanting to court developers to write swift programs, their hardware sales team doesnt seem to care about developer prosumers.
I have a college aged brother, and Microsoft currently owns GitHub, and is providing the linux subsystem, which is a huge signal that "developers are welcome." His whole generation is developing on $300 Dell laptops and it's easy. Mac used to provide that, but you paid for it.
* I need to develop for this shitty platform, which I hate, because my customers are on it
* I want to develop for this awesome platform, because I just love it and my customers are also on it
If Apple loses touch & favor with developers, their platform will slowly but surely die out over a decade or two. Apple is expensive, the only reason for Apple to even exist is because they deliver quality products. If they ever go down the road of consistently failing this core value, they will die more quickly than reindeer thrown down a cliff.
(Heck, technically, Mac developers don't even have to use Apple products to develop Mac applications. I've done native macOS app-dev and the only thing I have that runs macOS is a Hackintosh.)
Consider also this analogy: you don't develop console games on the console itself. You develop and build them on a computer using a cross-compiler, and then push them to a dev-kit unit to test them. Same thing applies here: just because you're writing macOS software, doesn't mean you need to be using macOS. You could stand up an office EXSi server running macOS VMs to serve as a CI server and test environment, and then actually write your macOS software in VSCode on Linux, pushing it over to the server to test it. People have done this. It's no harder than, say, developing for Android.