[BunsanSpace]

> MacOS has it's rough-edges, but it has become a pleasure to code on

Except when Apple deprecates APIs but the replacement doesn't have close to the same functionality (looking at you screen capture kit).

Or when the documentation just doesn't explain anything and you have to reverse engineer the API to figure out what it does.

or how there's a bunch of hidden APIs only certain vendors are told about so you can't even compete on an even playing field.

And don't get me started on the C, C++, ObjectiveC and now Swift monstrosities. Having fun with your legacy project when the new APIs require swift, so you have to use the objectiveC bridge and the weird bugs that comes with it.

[neuroelectron]

Also Apple undercutting your business by turning your app in an OS feature.

Or Apple deleting your app and account because of politics but they claim it's a policy violation. They just selectively enforce it.

Or apple allowing foreign governments back doors.

[BoredPositron]

Because Microsoft never did any of those things...

[neuroelectron]

Certainly not in the way Apple does. Archive/zip integration into the file explorer is a great example. As apposed to F.lux, where Apple completely removed the API and app and made their own version of it.

[pdpi]

GP said that macOS is a pleasure to code on, you’re arguing that it is not a pleasure to code for. Both can be true at the same time!

[bobbylarrybobby]

macOS is great to code on, not to code for