Thanks, Apple! Now go make your build tooling cross platform so we can just run it on a linux vm like everything else, and maybe stop gouging the people who are providing value for your platform?
Thanks, Apple! Now go make your build tooling cross platform so we can just run it on a linux vm like everything else, and maybe stop gouging the people who are providing value for your platform?
That seems high to me. Where does that come from?
> You typically make 1-3 PRs a day, each of which need to be built. Let's say 3 PRs + 1 build after merging.
That also seems like a lot, at least for an individual, which is what this seems? (to me) aimed at. I haven’t used it, but 25 hours seems within bounds for reasonable for a month’s usage.
> That seems high to me. Where does that come from?
it is high (and i agree too high imo), but many apps utilize a lot of 3rd party libraries that take a loooong time to compile (just off the top of my head, various "reactive" frameworks, realm, firebase related libs etc)you might ask why not deliver binary libs to cut down the time, well that used to be easy with obj-c/c dylibs but swift doesnt have a stable abi outside of apple libs, so every new swift update requires recompilation and swift package manager doesnt have much in the way of caching binaries for dependencies in a ci afaik
I’m currently working with a client to convince them Jenkins on a Mac they own is cheaper and easier, working through the standard headaches of an IT department who supports thousands of iPhones and Windows machines but doesn’t want to support a single digit number of Mac just because Apple fights any attempt at cross-compiling from anything that’s not a Mac.
a comparable clean build with debug flags (no optimization) might only take a few minutes with incremental builds taking a few seconds or so, i guess thats why its tolerated...
the other thing is ci build pipelines are reaaallly slow so if you made the same build locally on your m1 pro its probably gonna take 1/4 the time as the ci (ime anyways)...many ci's are slow af....
I don't know why it matters so much, but it seems to matter to them. I doubt the little extra money they made back then from selling to developers would have mattered to them?
But like all tech giants, Apple is now refocusing on services rather than software and devices, so perhaps forcing all Apple developers into their build service is part of that effort.
This step moves closer to a iPadOS Xcode solution for build, test and distribution. This has minimal demand on the iPad as long as the network connection is good enough.
Business acceptance of iPad is greater then that of Mac.
Looking forward to WWDC2024.
That sounds too awful to be true. Roughly how large are these average apps in terms of lines of code? I assume that's Swift rather than Objective-C?
I don't think they need to go as far as this. We already maintain windows CI agents on my team as we build C++ apps with MSVC. But crucially, our builds only take 10 minutes from cache, we don't want to pay for 24 hours usage.
Yeah, this is the killer. I don't mind paying $1/h for an M1 mac - our builds take about 10 minutes when cached, so paying $0.16 is fine. Even an hour's minimum would be totally fine - paying $60/mo to license it for 2h/day would be perfect. But, we're not paying $1/h with a 24h minimum every day. At that point, a Mac Mini is cheaper on month 1, so I have a mac mini on my desk.