|
|
|
|
|
|
by Karunamon
2804 days ago
|
|
|
That's non-responsive to the point of this particular paid update being one of the crappy ones. Eventually, he's going to have to shell out for the upgrade just to get something that had the right option in Xcode selected so he can still run it, despite an almost complete lack of new features or anything that actual development time was spent on. |
|
|
Or if he doesn't like it he could switch to one of the many other options. Or something open source, which can then be maintained himself if he wishes. That's part of the core point of open source you know? That one doesn't -have- to shell out for upgrades is why upgrades are good compared to subscriptions. If a developer puts out a bad paid upgrade, they get the most direct and unignorable form of feedback there is: less money.
>just to get something that had the right option in Xcode selected so he can still run it, despite an almost complete lack of new features or anything that actual development time was spent on.
Thanks for telling us that Apple promises backwards compatibility with all Mac software forever and that there are never any development maintenance of any kind required except "selecting the right option in Xcode". This was really news to me but will certainly make things a lot easier going forward now that I know nothing ever gets deprecated and removed from the OS over time.