I just bought a new m5 macbook air. The day that I can't treat my MacOS laptop as basically a glorified NeXT workstation and install/run code of my own choice (albeit after going through a few scary warnings in the default user protecting system preferences, like allow to run unsigned code, etc), is the day I stop buying apple hardware and just use linux laptops again.
I see news about apple thinking about "merging" MacOS and iOS and making a touch screen macbook and it really makes me think they are going to try to do this in the near future.
It is pretty clear where Apple/MS/Google OSes are headed, and it's a bad place.
At least computers of all other normal workers would be locked down; Those of developers could have development tools but certainly shouldn't be able to connect to production servers or have customer invoicing data in them. Maybe buy two computers for developers with legal tasks? Win-win for Apple.
Kinda tempted to do that already just because of Liquid Glass.
I mean, if I'm going to be stuck with a *nix OS whose UI is badly thought out and inconsistent between apps, might as well take the cheaper option, right?
Don’t worry. They’re working really hard to fix the bug. It’s not intended that you can install without paying a fee.
For now. It is clear which direction Apple is going.
One thing that ticks me off about this conversation is they are always framed as anti-consumer, instead of anti-developer. It's Tim Sweeney, Mark Zuckerberg, and the ad networks who have the biggest gripe with these policies, not consumers. Consumers are the ones who bear the brunt of the cost when it comes to developers who desperately need to exercise their right to capture every and any piece of data the OS provides.
>If I can download and run arbitrary code on my Mac--even if I have to jump through scary warnings--why should I not be able to do so on my phone?
We saw how developers used that "freedom" - now all almost all software runs in a remote server and is delivered through a sandbox (and even then developers try as hard as possible to poison that as well).
Evil developers forcing poor users to download their applications. Guess we all to suffer with braindead supercomputers in our pockets, because granny gran installed hax to get free gems for a gacha (that she downloaded from Apple approved App Store).
Stupid users who have neglected to attain perfect and absolute information regarding all the things that the applications they install will do.
thankfully the EU has extensive privacy regulations prohibiting developers from doing just that, so we can enjoy open platforms instead of being at the mercy of a private corporations protection racket as if it's the 19th century
Strictly speaking, you can. Enable developer mode, connect your phone to your Mac (you need a Mac), and you can build and install whatever code you want.
Asterisks being that your phone will uninstall it after a while I think, and you need to create a free account for Xcode.
And "whatever code you want" here excludes JIT compilation, or as I understand it memory that is both writable and executable, as your app would require a special 'entitlement' from Apple.
I considered getting an iPhone to replace my S-series Samsung, the only reason I stayed with Samsung is for the S-Pen. Had I gone with iPhone I would not be able to write and run my own software? That's absolutely ridiculous.
[0] Which is rare. I’m installing random shit all the time using homebrew and it’s basically never an issue.
If security was a concern, these hoops would be for all apps, not just unsigned. It just shows the only function it serves is gatekeeping by Apple.
> So for, say, your iPad mini plus 2–5 other iPads, the workable setup is: Mac + Xcode → $99/year developer membership → register each iPad's UDID → create an Ad Hoc build → install that build on those devices. You don't have to publish it, make it discoverable, or have Apple review it.
That would work for me, except that I prefer to build web apps instead. There’s nothing I really want to build that couldn’t be done as a web app.
As for why one computing platform would be different than another, if you don’t think there’s any difference then why not use a Raspberry Pi or something?
It would just be limited to 3 apps per device that require to be refreshed every 7 days to continue to be able to open them.
Web apps are a non starter for iOS since the only allowed browser on iOS happens to not support crucial standards and may drop your app's persistent data.
Yeah...
> then why not use a Raspberry Pi or something?
Because a Raspberry Pi would be very inconvenient to use as a smartphone, obviously. Doesn't explain why it makes sense to treat one ARM computer as a mildly locked jail (Macs) and another as a hard locked jail (iPhones and other handhelds); I feel like the only explanation here is that the smartphone duopoly has worked hard to condition customers into accepting this.
This is older than the current smartphone duopoly; IIRC, with a few exceptions like the N900 and the Palm Treo, cell phones were always very locked down. It probably came initially from the phone companies being control freaks, and wanting to restrict which devices (even mechanical ones with no electrical or radio interface) could be attached to their phone system.
> N900 and the Palm Treo
Performance-wise, a modern iPhone is more closely comparable to room-sized (building-sized?) supercomputer of that era.
If Microsoft had its act together PCs would have been just as locked down as phones are today and we wouldn't be questioning a difference.
I'm sad there was so much less backlash to restricting user control on phones.
https://www.nytimes.com/2003/06/30/business/technology-a-saf...
5% tax on all digital transactions (still applies to Kindle ebooks too I'm guessing?) and all applications have to go through an Apple review process. That's ridiculous for a government to explicitly agree to.
If that's the case then maybe we need to start considering what kind of alternate mechanisms can robustly mitigate the threat.
Because malware breaking the sandbox of one of them can mostly only spy on the owner, while malware breaking the sandbox of the other can spy on whoever the owner walks past, GPS trace their movements…
Question for those with more industry knowledge than me: If you assume a broken sandbox, is it possible for an app to record phone calls, then use that recording to create a deepfaked voice that can then be transmitted as a new call? My naïve assumption is "yes obviously", but for all I know the hardware has some way to activate a switched circuit from the phone service to the speaker and microphone that can't have other sound data pass through it.
Devices which only ran code that the vendor had specially packaged for the device always had other names, like Games Console, Word Processor, MP3 Player, Graphing Calculator, or just plain "Toy." Nobody confused those with computers and nobody accepted them as computers.
Phones entered this world already in that second category, long before Apple even considered making one. Apple kept an iron grip at first and after careful consideration, decided to only allow third-parties to even enter on terms extremely favorable and profitable to Apple, and always under their direct control.
Closing off the Mac would be very messy and also cause tremendous headaches due to it being the development platform for iOS. They don't want to bother. But the reason iOS is closed is because it's always been closed, and they'll never open it unless forced, because money.
Graphing Calculators are computers in every sense, it's hard to find one you can't at least program in a high level language like Basic or Python, and many accept assembly programs - even Texas Instruments models did, before their signing keys were brute forced.
Games consoles too almost invariably run third party code, although they tend not to be end user programmable - no different than an iPhone in that regard, really.
"Feature phones" - pre-smartphone phones with cameras and internet etc - usually had the ability to run Java Midlets without manufacturer blessing, even though you couldn't touch the OS. You could SSH into servers from those!
I think a big problem is that the distinction between "general purpose computer" and "end user programmable general purpose computer" is functionally meaningless when you can't write programs, which is most people. Instead they understand it in a functional context - what is this device for? How does it compare to how such devices usually work? The general purpose CPU inside is an implementation detail, and just because you think of an iPhone as a computer doesn't mean everyone does. They think of it as a "phone".
Then fix your s****y sandbox, Apple.
[Incoming call: National Security Agency] "Don't you dare stop our malware doing all that stuff you just said".
:P
All the other nations' agencies, outisde Five Eyes at least, will probably want to stop the NSA's malware, but may have their own instead.