Jeeshh Keith. That is NOT the main reason at all.
The main reasons are:
1) Time - I don't have time to constantly be fixing the broken builds in xSchedule. Every time you touch something there or add functionality or whatever, the build would break. Between day job, xLights updates, FPP updates, my store, becoming the primary educator for my kids (thanks to Covid, we'll be full remote for the next 2 months at least), etc... I don't have time to keep tracking things down for something I cannot even recommend anyone using.
2) Distribution channel - the PRIMARY distribution channel for xLights on the Mac is now the App store. App store apps are a single "app", not multiple. Right now, I have xLights there. At SOME point, I'd like to get xCapture and xFade as they are relatively simple as I kind of know what would need to be done for those (mostly around Menus and Icons, some layout things), but doing that takes a lot of time (see #1). Getting xSchedule in the App store would be nearly impossible without a complete redesign of the entire UI. (there is a separate question around the sandbox containers as well as some things like settings files cannot be shared from container to container).
3) Related to 2 and 1 - when flipping the project over to allow distribution from the app store, I had to nearly completely reset and rebuild the project file almost from scratch to have the proper settings and setup and all that for the app store requirements. (part of that was the project had been built up over many many years so had a ton of cruft) That took a lot of time and, again, not something I was willing to do for something I cannot recommend people using.
4) The number of people that even want xSchedule on the Mac is really low. The % of folks running xLights on the Mac (compared to Windows) is probably 8%ish. (assuming it's close to the normal market shares) Not really sure. The % of folks that use xSchedule compared to FPP is around 25% based on every recent poll. That said, I believe that number is even lower on the Mac since xSchedule has never really been promoted as supported on the Mac. Anyway, at best, 2% of the users want it. Again, my time is better spent on stuff targeting a larger audience.
5) For very low cost (~$50) you can get a very very good player/scheduler/etc... that performs just as well as xSchedule, has pretty much the same feature set (FPP has some things xSchedule doesn't and vice versa), and is known to work extremely well and can scale from small little displays up to gigantic displays.
6) And if you NEED to have something running on the Mac, FPP runs very well in Docker on the Mac. I actually use that for much of the development. Definitely something that needs more documentation for folks that aren't aware of Docker or have used it before, but if you have Docker desktop installed, getting FPP running in Docker only takes a couple minutes (mostly downloading).
Anyway, I strongly recommend giving FPP on a Pi a chance. Since FPP is used in most shows anyway in one form or another (controllers, Panel matrices, projectors, etc...), it would be a good thing to experiment with and learn anyway.
