4 ms·
>aside from being a developer for Apple's platforms who occasionally looks around for CI services So, you give him all this shit and you're not even using his
by coldtea 6y ago
>aside from being a developer for Apple's platforms who occasionally looks around for CI services
So, you give him all this shit and you're not even using his service?
>There's still a huge hole for a service that lets you rent a Mac for the a couple minutes so you can build your Xcode project. It's not your fault that doesn't exist, it's Apple's.
If we're talking for CI of builds, sure. But in that case, one wouldn't be much affected (the C in CI means continuous, so you wont just rent for a few minutes).
Otherwise, as a user, I'm quite satisfied with less developers being able to build XCode projects and submit apps without even owning a Mac to test them on. Looks like it would bring a delluge of poorly ported apps based on cross-platform APIs and only tested in non-Mac platforms (if that).
- hobs 6y agoI like you and I think your posts are generally high quality, so I am going to say that an elitist "screw people who cant afford an overpriced mac" is not a good thing imo. Will we get some lower quality apps, sure, do those already exist? yeah. It just sounds like gatekeeping for not much benefit.
- shiftpgdn 6y agoIt's important developers (or their QA people) be able to use the device they're publishing to.
- hobs 6y agoIs that why web developers have their hands on every iteration of every device on the planet? Or do they have some sort of tooling that emulates that experience for them?
- coldtea 6y ago>I like you and I think your posts are generally high quality Thanks! I try to add the ocassional low quality comment for balance :-) >so I am going to say that an elitist "screw people who cant afford an overpriced mac" is not a good thing imo. Well, my intented meaning was more like "Don't create/sell apps for a platform you dont even own to test in". The main reason to go for "by the minute" builds on the Cloud for a machine you don't own is to either help with porting to an architecture you don't use, or to churn apps with some cross platform framework to a platform you don't use/care about. I think the latter would be more frequent. If they were mere poor hobbyists guys legitimately coding for the platform, they'd own a machine, either new, or second hand, or whatever. It's when you don't code in the platform, but only want to target it for selling that you have an issue...
- williamscales 6y ago> The main reason to go for "by the minute" builds on the Cloud for a machine you don't own is to either help with porting to an architecture you don't use, or to churn apps with some cross platform framework to a platform you don't use/care about. You can also go for "by the minute" builds on the Cloud for a machine you do own. Suppose the developers and testers have Macs on their desks, but you still want to have your CI run in the Cloud. Now I'm not an expert on cloud pricing so I could be wrong, but I imagine you could benefit from paying by the minute in that case, depending on the specifics of your situation (builds per day, time per build, total cost of ownership of having a build farm in house).
- durandal1 6y agoIf cost is a barrier to entry, then an old used Mac is going to be significantly cheaper than any AWS offering.
- saagarjha 6y agoYes, I think I reserve the right to judge him for a decision that hurts iOS/macOS developers as a whole. Can't I judge Facebook for being a privacy violating nightmare even though I've never had an account with them? As for your other comments: I know what CI is; I use it daily! The way my CI runs (which is how most CI is!) is that a when a commit gets pushed a machine gets spun up to build it, then a few minutes later it shuts itself down once the compilation is complete. Why would I want to pay to have a Mac for an entire day in this scenario? I'd have to be pushing code every few minutes to have any hope of efficiently using one machine. And believe me, I hate cross-platform garbage apps just as much as you do. But I am not in favor of putting arbitrary restrictions on how people can write their apps. Xcode used to be a soft-requirement to build apps and look how well that worked out: native developers have to stick with it all the time, even when it's acting up and being buggy, and developers who couldn't care less have reverse engineered it to the point where they either generate an Xcode project from a source tree and build from the command line, or they just package their own app bundle themselves with the magic bits that Xcode would usually apply. Trying to stop people from making garbage apps by limiting their tooling options rarely works. And, in fact, I personally know people who go services like MacStadium (VNCing in) to use Xcode for the couple days it takes to set up a build system with the right certificates and profiles, then they never touch a Mac ever again. It's the native developers with their own Macs who want to use a fresh machine to build their code for Mojave or something that they aren't running on their personal computers.