Outside of TenFourFox and Roccat, does anybody know of modern macOS apps being written with PPC support built into their development?
Surely it can't be a huge undertaking to plan and span compatibility between Leopard PPC and Sierra.
Regardless of the move to Swift, the Objective-C language only went through minor syntax changes for simplifying NSNumber and NSArray/NSDictionary interactions. However, the older syntax still works in modern Xcode.
C Blocks are the only major architectural change to the Objective-C language that I'm aware of post 10.5 and there is a project called PLBlocks which brings full 10.6 style Blocks to the Leopard SDK.
This makes injecting block code for callbacks and NSOperationQueue messages equal in syntax and run time handling.
Perhaps I'm overlooking something and it is a major pain in the ass to run an intel x86_64 macOS project in parallel with PPC, but app developers have been running macOS and iOS apps off the same code base for years and those two systems run on different architectures with separate frameworks using totally different user interactions and interface guidelines. I know AppKit and UIKit have mostly the same principals but still use different methods and only similar syntax to achieve similar results.
Is PowerPC really that minuscule of a niche market that developers have absolutely no interest in supporting these still-capable systems?
*rant over*
[doublepost=1501946182][/doublepost]*rant continued*
Orrr... Is it a matter of developers not wanting to be held accountable for supporting an operating system which the mothership has marked as no longer secured?
As in; Windows XP was marked as dangerously unsecured the moment Microsoft gave it a funeral and people were advised not to even poke it with a stick in case of a highly contagious flesh eating virus.
However... XP still works and it didn't self-combust.
It may come as a surprise to the hot shot iOS gold-rush diggers who "advanced" their skills to include macOS in their development portfolio as an afterthought to plastering their tapitytap success story to every mobile platform out there, but;
[macOS isEqualTo: @"Mac OS X"] == YES;
... it's the same operating system with an updated SDK, regardless of the underlying architecture!!
We don't need any more Mac apps ported from the iPhone with an interface rewrite. We need quality desktop "Applications", which serve a need for productivity and creativity and not just more and more consumerism!
*now I'm done*
Surely it can't be a huge undertaking to plan and span compatibility between Leopard PPC and Sierra.
Regardless of the move to Swift, the Objective-C language only went through minor syntax changes for simplifying NSNumber and NSArray/NSDictionary interactions. However, the older syntax still works in modern Xcode.
C Blocks are the only major architectural change to the Objective-C language that I'm aware of post 10.5 and there is a project called PLBlocks which brings full 10.6 style Blocks to the Leopard SDK.
This makes injecting block code for callbacks and NSOperationQueue messages equal in syntax and run time handling.
Perhaps I'm overlooking something and it is a major pain in the ass to run an intel x86_64 macOS project in parallel with PPC, but app developers have been running macOS and iOS apps off the same code base for years and those two systems run on different architectures with separate frameworks using totally different user interactions and interface guidelines. I know AppKit and UIKit have mostly the same principals but still use different methods and only similar syntax to achieve similar results.
Is PowerPC really that minuscule of a niche market that developers have absolutely no interest in supporting these still-capable systems?
*rant over*
[doublepost=1501946182][/doublepost]*rant continued*
Orrr... Is it a matter of developers not wanting to be held accountable for supporting an operating system which the mothership has marked as no longer secured?
As in; Windows XP was marked as dangerously unsecured the moment Microsoft gave it a funeral and people were advised not to even poke it with a stick in case of a highly contagious flesh eating virus.
However... XP still works and it didn't self-combust.
It may come as a surprise to the hot shot iOS gold-rush diggers who "advanced" their skills to include macOS in their development portfolio as an afterthought to plastering their tapitytap success story to every mobile platform out there, but;
[macOS isEqualTo: @"Mac OS X"] == YES;
... it's the same operating system with an updated SDK, regardless of the underlying architecture!!
We don't need any more Mac apps ported from the iPhone with an interface rewrite. We need quality desktop "Applications", which serve a need for productivity and creativity and not just more and more consumerism!
*now I'm done*
Last edited: