[filleduchaos]

It seems even stranger to me to consider it an active effort.

More likely to me that engineering teams at Apple simply don't give much of a shit about maintaining compatibility with a tool that's not affiliated with them, and will redesign things or make breaking changes as it suits their project goals - and unaffiliated tools like this are simply stuck in a perpetual game of catchup.

[smoldesu]

> and unaffiliated tools like this are simply stuck in a perpetual game of catchup.

So it's still a problem. Apple knows about these unaffiliated tools, and they do very little to maintain communique with them until it's convenient for Apple to do so. This is nothing new, and it's one of the reasons you couldn't pay me to develop on iOS these days.

[filleduchaos]

But why should they maintain communications with them? Don't get me wrong, it would certainly be nice of them to, but I don't see how someone else doing unaffiliated, unrequested, unguaranteed work based on my own work creates any sort of obligation for either of us.

[smoldesu]

I figure that it would be a good way for the world's most valuable company to give back to their core userbase, and it would certainly be a step in the right direction for helping developers like me who are highly skeptical of Apple's commitment to building a robust developer ecosystem. They need all the help they can get, because it's starting to look less and less viable for me to switch to a Mac as time goes on. It will be interesting to watch how they reconcile pressure from developers over the next few years.