Apple's 15% Deflection Tactic

Re:Apple's 15% Deflection Tactic by jolux on Wednesday November 18, 2020 @07:20PM (#25144594)

I pay more for iPhones partially because the ecosystem is not yet fully crapped up with C++ programs with bad UIs, and I think Apple would argue this point too. You’re fully allowed to draw your UI with Metal though, and MoltenVK supports iOS. Many iOS games use almost no platform UI components.

[ Parent | on HN ]

Re:Apple's 15% Deflection Tactic by kevingadd on Wednesday November 18, 2020 @10:10PM (#25145786)

Sure, but the argument becomes circular, doesn't it? They deserve X% because you use their APIs, and they force you to use their APIs. Congratulations? If it's so expensive to develop/maintain those APIs that they can't afford to part with them for less than 30%+cost of hardware, maybe they shouldn't require you to use them?

[ Parent | on HN ]

Re:Apple's 15% Deflection Tactic by jolux on Wednesday November 18, 2020 @11:41PM (#25146293)

You’re not required to use them though, as I just explained. What you can’t do is write to memory and then execute it, because that’s a security risk.

[ Parent | on HN ]

Re:Apple's 15% Deflection Tactic by saagarjha on Thursday November 19, 2020 @05:27AM (#25148044)

That's not a security risk, it's a "makes App Review potentially pointless" risk.

[ Parent | on HN ]

Re:Apple's 15% Deflection Tactic by jolux on Thursday November 19, 2020 @09:35AM (#25149881)

How is it not a security risk?

[ Parent | on HN ]

Re:Apple's 15% Deflection Tactic by saagarjha on Thursday November 19, 2020 @04:40PM (#25154724)

How is it one? It’s not like the ability to JIT magically lifts the platform sandbox.

[ Parent | on HN ]