Live data from Hacker News

Apple agrees to settle potential class action suit by U.S. developers

axios.com

211–220 of 259 posts

Re: Apple agrees to settle potential class action suit by U.S. developers

#211

I don't understand why the App Store, this small "side business" in the grand scheme of things, is something Apple is worth fighting and dying over. It's literally, a small fraction of their revenue, and yet it grabs 80% of the bad PR and is now under investigation and proposed legislation in the US, UK, EU, Korea, and I think Australia. If I'm Apple, shouldn't it be obvious at this point that losing the App Store mo…

> If I'm Apple, shouldn't it be obvious at this point that losing the App Store monopoly is inevitable? I think Apple believes their own PR story here. They really do believe that the App Store is great for everyone, not just them. They really do believe that they're entitled to a generous cut of all transactions that happen on their devices. Objectively, you're right -- although I think I'd go farther and suggest th…

> probably not enough to be worth the risk of going through what they're facing now.

Easing restrictions over the years wouldn't prevent the inevitable. Doing it this way lets them face the inevitable lawsuits from a position of power, rather than a weaker position after years of slowly easing restrictions.

It's like ripping off a bandaid.

Re: Apple agrees to settle potential class action suit by U.S. developers

#213

> Developers can communicate directly with customers about alternative payment options. Customers have to consent and be given the right to opt-out. This is a huge step forward (though it falls well short of the ideal case) for iOS development. Having the ability to tell customers about other, often cheaper, payment methods removes a substantial barrier for some apps that have high-priced subscriptions. Positive as t…

I have the same concern as well. Apple won't change a damn thing unless a US Court backs anyone but them. If you have legal precedence of a loss on Apples part, they won't be able to pull this BS in the future.

Re: Apple agrees to settle potential class action suit by U.S. developers

#215

Earlier quoted context omitted.

Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.

In a triple A game I worked on, the PlayStation button enums were CROSS, SQUARE, TRIANGLE, and...... CRIRCLE. Would drive me absolutely livid. But of course no one was allowed to fix is since it was already in a few different games, countless script files, network-controlled configs etc.....

A very long time ago we outsourced our Wordpress development and customization to a developer we found on a website who was from Moldova. He did pretty decent work and we got a great deal, but the HTML/CSS was a bane to work with. Almost half the DIV id's and such were spelled slightly wrong. Didn't affect the operation of the site but was very annoying to work with.

Re: Apple agrees to settle potential class action suit by U.S. developers

#216
post #56

Earlier quoted context omitted.

Complete with spelling errors, semicolons in place of commas, shouting snake case, and unnecessary explicit numbering. Definitely enterprise-grade.

When somebody comes along and inserts a new case next to an existing case because they're closely related, you'll be glad the numbers are explicit.

Negative - if these are going to be treated like keys where the integer value needs to retain the same meaning between builds, then an enum is the wrong abstraction to use.

Re: Apple agrees to settle potential class action suit by U.S. developers

#217

Earlier quoted context omitted.

It'll be as it has always been. Apps can't show or hint at alternative payment options. This is in regards to letting users know about such options outside the iPhone's scope (email for instance)

I was hoping Apple was ceding some ground in this, it’s what puts the dirtiest taste in my mouth. If you go to even Walmart (a company very strict on their suppliers) and pick up some object, on the back of the packaging will be www.exampleproduct dot com. And on that website you could theoretically sell your product directly. What does Apple do? “Oh on that privacy policy we mandated you could click here and then he…

But Walmart wouldn’t let a vendor set up a kiosk in the middle of the store and accept payments with a Square reader on a phone, would they?

Re: Apple agrees to settle potential class action suit by U.S. developers

#218
post #101

Earlier quoted context omitted.

I used to do technical writing and for some software that I wrote the manual and help system for, one of the menu items was misspelled. I spelled the word correctly in the text describing its functionality, but whenever I referred (so to speak) to it directly as the menu item to be selected, I kept the misspelling (this was the early 90s, the days of people saying non-ironically that they couldn't find the "any" key…

Pretty sure people still can't find the any key, we just stopped asking them to!

Yep, I get some prompts now that say "Press the $X key" (often space), but will actually proceed if you hit any key. It always give me a touch of chuckles when I think about why they named a specific key then.

Re: Apple agrees to settle potential class action suit by U.S. developers

#219

Earlier quoted context omitted.

Lol, few things trigger my OCD more than misspelled words in identifiers. I legit missed important use case while amending legacy system just because someone decided to have “priveleges” in the variable name. I hope all those ways to spell number 90 are part of the joke.

I worked with a (home-rolled at the company, but long before my time with no compilation documentation) comms library that had functions named "receive" and functions named "recieve". Even better, the library was called into as a COM object by a Visual Basic Script script, and the misspelled corner case only got hit rarely. Figuring out that the problem was the correctly spelled function call was a joy.

I rarely work with Excel. A couple of days ago I had the joy to need to apply a function with multiple parameters. The formula parser complained with an error message which meant nothing to me. I finally figured out that I needed to use semicolons as separator for the function arguments (I am from Germany). Who in his right mind does THIS? I tried to change the separator in Windows setting, to no avail.

Re: Apple agrees to settle potential class action suit by U.S. developers

#220

Earlier quoted context omitted.

At this point most students learning about that number assume it's misspelled when first introduced and incorrect the teacher.

>>incorrect the teacher. Did you just use incorrect as a verb?

A favorite pastime of HN is users incorrecting each other on topics they know nothing about. ;)
Post reply on HN