|
|
|
|
|
|
by AsyncAwait
2744 days ago
|
|
|
> The really tricky problem is when a package must modify an existing shared resource. Such as appending lines to an existing config for example. A big part of Librem 5's mission is to be secure and private, but perhaps even bigger part is to be FLOSS and hackable, so one could use any host and any stack to develop pretty much anything they could on a standard GNU/Linux distro. Locking down iOS/macOS may improve security, but doesn't give you access to the source code, does not protect you from Apple and does not free you from the limitations they've put on you as a developer, or going via their-own distribution channels for that matter and having complete control over your future if you're an iOS developer. So it all depends on why you're exited about the Librem5, but if openness, FLOSS, hackability are any part of it, then locking down Apple hardware wouldn't do it. |
|
|