Beyond the user freedom angle, this could also help reduce e-waste as there will be a niche but functional ecosystem of tools to keep the phone or games console (!) running past it's lifecycle
Beyond the user freedom angle, this could also help reduce e-waste as there will be a niche but functional ecosystem of tools to keep the phone or games console (!) running past it's lifecycle
The whole notion of what qualifies as a quasi-pc is an incredibly slippery slope. Game consoles would qualify as that and given how the lifetime profitably is made up in game sales, having third party app stores would potentially be ruinous for Sony/Microsoft/Nintendo. The incentive to spend a lot on hardware innovation disappears when the profits are dried up. Legislation based on business practice just gets to the point of being asinine. Should Apple be forced to sell hardware at a loss or near cost in order to have the privilege of having a walled garden?
The user freedom angle here is that people want their walled garden. Personally, I’m happy with the payment security it provides and a decent guarantee of privacy. I’m not sure you realizing that you’re asking for that to be taken away from me and many others who like it how it is.
There's no way for the consumers to decide when there are only two options, especially because those options are not interchangeable.
It's not like some other company can say "I'm going to make a competitor to the iPhone, that can run all of the same iOS apps, but mine will allow third party app stores!".
I think this is a point that people who advocate for breaking down the walls of the Apple garden don't adequately consider. The iPhone is not really comparable to the desktop computer you could do whatever you want with in the 1990s. It's basically an extension of the person, with all their bank, emails, locations, web history. To make it a truly "open" platform, it would open its users -- who trust them -- to these kinds of problems, and would need to somehow solve them for those customers in a way that doesn't run afoul of the "open" aspect that people demand. That's a tightrope that becomes very difficult to walk when the headlines read "Apple app let hackers steal bank details, enable widespread fraud." It doesn't matter that it wasn't an Apple app. It doesn't matter that that App was downloaded on a 3rd party App Store. It doesn't matter that the user tapped through a dialog that said "This is a third party app that doesn't have Apple's protections on it, be careful!" Those are all nuances that are lost in that headline.
It's asking Apple to risk the privacy of their users and their business profits, so that people can have marginally cheaper apps.
I think the only way forward, really, is the model where smaller developers don't have to pay a fee until they reach $1m in sales. That tiered approach seems reasonable; after all, there's no reason to let huge developers off the hook for paying their fair share to keep the system running.
One immutable set of toggles, and then an infinite variety of suggested settings for those.
It's not clear to me that's as true any more, when, randomly for instance, HEVC is in chips, or iPhones include an ASIC that's actually an FPGA.
This seems to require a new principle, that a device maker may decide how far up the stack their logic goes, regardless of the form in which that logic is represented.
As a check and balance on this, perhaps device makers do not get to retroactively (for a given device) take back intentional open parts of that waterline, as we've seen console makers do with what were deliberate and marketed capabilities, sometimes long after release.
Ignoring that it would be pretty wild if I could actually throw Verilog (Yuck) at my phone, I would draw the line at roughly the OS kernel or at least it's rough outline. The OEM wouldn't be allowed to include any time bombs under that layer, but ultimately the focus is on "day to day" work rather than complete control of the hardware.