[sorbits]

While you only have to update your build process once, you now have a noticeable delay for every single release build, and worse, a few times per year, your build will break because you haven’t signed Apple’s latest contract.

And for what? There is no way Apple can make it impossible to get malware notarized.

[Klonoar]

But your release build is not done constantly, and so you have to sign in and accept an agreement - neither of which is a big deal.

[hansvm]

> But your release build is not done constantly

Some people (are they the minority? probably?) cut release builds frequently enough for it to be a big pain point.

> and so you have to sign in and accept an agreement - [which isn't] a big deal

It probably is though. Have _any_ agreements you've accepted in the last, say, 5yrs not had blatantly overbearing or malicious terms?

[Klonoar]

If you're cutting release builds often enough that the extra minute or two is hampering your productivity, you may have bigger issues with software development.

[sorbits]

For me, it is generally > 2 minutes, and “release build” cover any build that leave your machine, e.g. nightly builds, beta builds, test builds to a specific user to track down some issue, etc.

Signing the agreement is also not just clicking “Agree”, you have to hunt for the contract online first. Last time I did this, their 2FA was down, so just logging in took me about a minute.

It feels like a lot of friction that serves absolutely no purpose, which makes it so extremely infuriating.

This is from the same company whose former CEO pressured a developer to reduce the boot time of the Macintosh (and got a 28 second speedup).

Yes, this stuff really matters to a lot of us!