Skip to content

Category: Apple

How do people develop for MacOS at scale?

So, how do people develop people for MacOS at scale?

Normal people throw compile jobs at their Kubernetes cluster, and fan out a compile across some two racks full of 50 core machines, giving you some 4000 cores to play with for distributed compiles.

Is there a MacOS LLVM docker image that runs the Xcode compiler in Linux containers and that can be plugged into this? Or are people piling Mac mini and Mac pro or other unrackable bullshit with insufficient remote management into racks, creating a nightmare farm of snowflakes?

How does Apple itself do this? Like animals, on the Desktop?

And how do you integrate such a remote compile farm into Xcode?

9 Comments

Moving from 1Password to Enpass

In order to move customers from a “purchase a license” to a subscription model, AgileBits is experimenting with dropping support for local vaults, requiring cloud storage of passwords.

There is a lot of blowback in Blogs and the 1Password support forums. Also, the security professionals on Twitter frown on this, quite a bit (Thread).

Discussion on Facebook pointed to Enpass, and that is actually looking like a pretty good 1Password clone.

Enpass on Mac, Main Screen
10 Comments

Our coming Copyright Overlords

According to the New York Post (yes, I know), Apple’s Eddy Cue are looking to improve the original video strategy Apple has (most likely in reaction to Netflix and Youtube). The wording is worrying:

While at least one of the discussions between Apple and an executive was vague when it came to the tech company’s ultimate goal, the executive was left with the impression that the Cupertino, Calif., company is looking for a transformative acquisition and not just a deal to buy TV shows.

and later

“They talked to Sony and Paramount last week. They are preparing something big,” a source told The Post.

Nobody has anything concrete at the moment, though.

Leave a Comment

App can’t be opened because the identity of the developer cannot be confirmed

Policy Settings can prevent the execution of unsigned binaries.

MacOS can be set to prevent the execution of unsigned binaries. This is done by pushing a security policy to the system, which is then enforced by the SecAssessment subsystem.

Of course, you can still install XCode and compile binaries locally, and even execute them. You can also code in interpreted languages such as the local Python, and call system functions from there, so the policy is only of very limited use in locking down the system.

9 Comments