2 ms·
I did, and I'll highlight the relevant sections of your comment for you. > I've been through the same hell and there's basically just one way to publish softwa
by Klonoar 3y ago
I did, and I'll highlight the relevant sections of your comment for you.
> I've been through the same hell and there's basically just one way to publish software for macOS with no hassle for the user: Completely lock yourself in their ecosystem. That means working on a Mac, building in Xcode using Swift and publishing in the official app store.
Your highlighted portions are false.
- coldtea 3y agoYeah, as is "If you really need to publish on Mac for whatever reason, it is so much better to dump the hassle on the user.". All those other devs, including tens of thousands of MacPorts and Homebrew ports, manage to not dump any hassle to the user...
- ehutch79 3y agoArguably, relying on homebrew is dumping the hassle on the user. To be honest though, if your making a cli tool, you’re requiring the command line. And anyone comfortable with the command line can install homebrew