Erase your darlings: immutable infrastructure for mutable systems

Re:Erase your darlings: immutable infrastructure for mutable... by joshspankit on Monday April 13, 2020 @02:43PM (#22858652)

Permissions fails because if your user has the ability to read the application’s files, they can copy it. If they cannot, then neither can the application itself (aka it cannot run).

Demo versions (as in compiled to be a limited demo) are viable, but was counter to Apple’s image at that time (it doesn’t really show off the experience if you’re getting restricted or nagged).

[ Parent | on HN ]

Re:Erase your darlings: immutable infrastructure for mutable... by mixmastamyk on Monday April 13, 2020 @02:51PM (#22858757)

Read yes, but not write to removable drives. This setting is used on every machine in a VFX company I worked for. Although, I don't know how supported it is across platforms.

[ Parent | on HN ]

Re:Erase your darlings: immutable infrastructure for mutable... by joshspankit on Monday April 13, 2020 @10:23PM (#22862181)

Right you have a possible win there. Totally slipped my mind since it’s not currently available.

Apple stores still need to allow people to connect their iOS devices and maybe USB sticks for photos, but they could have created a “read-only” policy and applied it to store machines.

Of course, these days they just distribute through the app store, and those apps put tentacles all over the place. No USB copies would function.

[ Parent | on HN ]

Re:Erase your darlings: immutable infrastructure for mutable... by girvo on Tuesday April 14, 2020 @12:24AM (#22862730)

Weirdly, an app I purchased on the App Store ran perfectly fine copied to my friends Mac. I wonder why?

[ Parent | on HN ]

Re:Erase your darlings: immutable infrastructure for mutable... by oefrha on Tuesday April 14, 2020 @01:36AM (#22863023)

The license check is opt-in on the developer’s side.

https://www.objc.io/issues/17-security/receipt-validation/

[ Parent | on HN ]