by ArmandGrillet on 1/26/21, 9:38 PM with 13 comments
by chmaynard on 1/26/21, 11:32 PM
The moral of this story is clear but third-party developers for Apple devices don't want to face it. With a few exceptions, most Apple frameworks and application software are proprietary. If Apple's internal source code is deemed to be central to their business, outside developers will probably never get to see it. And if they can't see it, they can't fix and improve it.
If you write application software for Apple devices, you have made a Faustian bargain. You are at the mercy of the whims of Apple Software Engineering; Apple has you by the proverbial balls. If your own code is also proprietary then your customers are in the same vulnerable position, so stop complaining.
by washadjeffmad on 1/27/21, 12:49 AM
When I wished for MacOS to become more Linux-like, I regret not specifying how or when.
by Jyaif on 1/26/21, 11:43 PM
by andrewmcwatters on 1/27/21, 3:15 PM
I publish an app that works on Windows, Mac, and Linux, but if I ever ran into a situation like this repeatedly, I’d just kill the feature on that platform and save my engineering hours for something more important.
I’m interested in what Apple is going to do for me, I’m not interested in enriching their platform.
by alfonsodev on 1/27/21, 12:08 AM
by DoofusOfDeath on 1/27/21, 2:44 AM
Is that just known to be so pointless that it's not worth mention?