← Back to context

Comment by cosmic_cheese

4 hours ago

I think this is one of those cases where “build it and they will come” applies.

The corporate giants are their own thing, but indie/small Mac devs are among some of the most steadfast early adopters in the software world. They routinely have new releases leveraging whatever new things were added at WWDC in the span of a few weeks or months. Many would be thrilled by a project that promises to bring back what they loved about OS X and would be happy to contribute.

The only problem is that the “it” that needs to be built is a set of frameworks that’s as robust as Cocoa/AppKit is, is flexible with language use (Mac apps have long rolled in C, C++, Ruby, and Python alongside Objective-C or Swift for UI), and isn’t afraid to be opinionated (a single well-supported “happy path” to do something is better than a dozen halfassed ways). That’s really the hardest part.

As for Tiger, on the Ryzen box you might get better performance from a hackintoshed x86 build (especially if you’ve got a spare PCI slot for passing through an old supported GPU for UI acceleration).