mike eggleston

Maybe it has been a while since going over the ApplePay developer docs and what not; but I don’t recall that the developer is charged with a fee from using ApplePay, any sort of fees come from the credit card companies. As such, it seems to me like the EU is making a false claim here. Are they going after Google for GooglePay? What about Samsung and their SamsungPay? Wait, what about WalmartPay (which I can do from my iPhone)?

This seems like complete bullsh*t, if you ask me.

Fred257 said:

I’m, they already have a chip that’s faster then Apple Silicon.

https://www.gearnews.com/intel-alder-lake-mobility-chip-better-performance-than-apple-m1-max/

The problem with that is that their presumably not shipping desktop chips are barely outpacing Apple's shipping M1 Max Laptop chips! To put it mildly, it is a false-equivalency at best. To quote The Great One: Skate to where the puck is going to be, not where it is.

Mike Wuerthele said:

j2fusion said:

Is anyone surprised by this… anyone?

I wasn't, but it's good to have proof.

Epic hasn't responded to our emails and questions about it, and I'm not expecting them to.

To be fair, this honestly doesn't surprise me at all. I thought that the Coalition for App Fairness was a sham to begin with. Seeing that it is definitely a sham associated with the other sham known as Sweeney; can we finally start blasting that company publicly about this very plainly obvious affront to contractional agreements?

Cannot get at the VSCode extensions either.

docno42 said:

Seriously?  Rouge Amoeba, who has been a Mac developer for decades, can't be trusted with private API access?  

Apple are a bunch of cowards hiding behind policy - that they created!  Why does everyone have to be treated the same?  Answer: they don't.  But it's far easier to treat everyone the same.  No critical thought required - just numbly point to the policy, claim your hands are tied and then conveniently ignore the fact that you made the policy that is tying your hands in the first place. 

I only picked this part of your tirade of a comment, because it seems like it is the core of it. That said, I am not sure where to start with this. So, I will begin with where my strengths are, and that is backend programming.

I develop APIs and backend processes for a living, and I can tell you with unequivocal certainty that having a set core of rules that all of your users of APIs have to abide by is CRITICAL to making sure that people who develop for your platform do so in the way that you intended. Those policies are the very foundation that make a secure platform that works not just for the developers but also for the users who use it. That is why they have those policies. Yes, some people want side-loading apps. That doesn't make it the correct solution. The moment a bad actor comes in and does something, who do you think the public (the same public demanding for side-loading apps) will blame? That's right, the people who made the APIs in the first place (that would be Apple).

So while it is fun to complain about how Apple doesn't trust "respected developers" or they are "limiting my choice" or whatever nonsense you want to spew out next; the fact of the matter is that they created an environment that is secure, user-centric, and accessible as long as you are willing to play by the rules. Yes, those rules are malleable and can change; but as they are written right now, those are the rules.