Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

axios.com

Post reply on HN
Print view View original

181–190 of 259 posts

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

#181

Post by TheNewAndy »

jrockway wrote: post #48

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

There is some evidence of this - if you can log in to app store connect (need a developer account) there is this page:

https://appstoreconnect.apple.com/apps/pricingmatrix/1539646...

It shows the tiers from 0 (free) to 87 (USD 999).

Then come the party tiers: 510, 530, 550, 560, 570, 580, 590 which are just repeats of the other tiers, probably for some good historical reason which I'm not aware of.

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

#182

Post by objclxt »

TheNewAndy wrote: post #181
jrockway wrote: post #48

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

There is some evidence of this - if you can log in to app store connect (need a developer account) there is this page: https://appstoreconnect.apple.com/apps/pricingmatrix/1539646... It shows the tiers from 0 (free) to 87 (USD 999). Then come the party tiers: 510, 530, 550, 560, 570, 580, 590 which are just repeats of the other tiers, probably for some good historical reason which I'm not aware of.

> which are just repeats of the other tiers

Those are the price adjusted tiers. They look like repeats in USD, but if you look at other currencies you’ll see they’re different. They’re designed to allow you to offer price points that are scaled according to the market (i.e, 99c in the US, but considerably cheaper than that in India or China).

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

#183

Post by TheNewAndy »

objclxt wrote: post #182
TheNewAndy wrote: post #181

Earlier quoted context omitted.

There is some evidence of this - if you can log in to app store connect (need a developer account) there is this page: https://appstoreconnect.apple.com/apps/pricingmatrix/1539646... It shows the tiers from 0 (free) to 87 (USD 999). Then come the party tiers: 510, 530, 550, 560, 570, 580, 590 which are just repeats of the other tiers, probably for some good historical reason which I'm not aware of.

> which are just repeats of the other tiers Those are the price adjusted tiers. They look like repeats in USD, but if you look at other currencies you’ll see they’re different. They’re designed to allow you to offer price points that are scaled according to the market (i.e, 99c in the US, but considerably cheaper than that in India or China).

Makes sense, thanks.

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

#184

Post by UglyToad »

mynegation wrote: post #54
jrockway wrote: post #48

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

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.

This reminds me when I was learning to code I was working through the Project Euler problems in python, one of them has you write code to do something with the English words for numbers.

I wrote my code and was fairly confident it was correct, submit the answer and it is rejected, spend the next few hours trying to find the logic error. Of course it's because English is ridiculous and it's "forty" instead of "fourty".

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

#185

Post by ballenf »

etrautmann wrote: post #171
hnlmorg wrote: post #169

Earlier quoted context omitted.

I feel your pain. A company I work for has a weird name that doesn't follow the rules of English spelling correctly (I can't say more without giving away the company name). This was an intentional decision and poses enough of a problem for guests visiting the company. But the absurd thing is this company decides to double down on it's troubles by naming all of it's projects using the same broken rule as the company t…

Googol?

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

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

#186

Post by mastazi »

hnlmorg wrote: post #169
gambiting wrote: post #149

Earlier quoted context omitted.

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.....

I feel your pain. A company I work for has a weird name that doesn't follow the rules of English spelling correctly (I can't say more without giving away the company name). This was an intentional decision and poses enough of a problem for guests visiting the company. But the absurd thing is this company decides to double down on it's troubles by naming all of it's projects using the same broken rule as the company t…

I see what you did here...

> it's troubles

> it's projects

> So now I'm often finding myself misspelling common words

> And all of this is intentional too!

:-D

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

#188

Post by chrisweekly »

btilly wrote: post #116
dhosek wrote: post #97

Earlier quoted context omitted.

There are lots of ways for spelling errors to get reified. They can also end up in a data interchange XML schema (I bumped into that one at a previous job where it seemed like an obvious and trivial fix to correct the spelling of a class name and discovered that it had ended up in a company-wide data interchange schema which could not be practically fixed).

The most important example of that class of error is REFERER. It should have been spelled REFERRER. But nobody caught it, and you really can't change something that is part of the HTTP standard...

Tangent: this reminds me of the _aptly_ named "mod_speling" module.

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

#189

Post by mananaysiempre »

Someone wrote: post #138
dhosek wrote: post #100

Earlier quoted context omitted.

Lets not forget the misspelling of guillemet as guillemot that is now firmly embedded into PostScript and Adobe software with no chance of ever being fixed. Unicode sidestepped the issue by naming the characters RIGHT/LEFT-POINTING DOUBLE ANGLE QUOTATION MARK.

Unicode also documents its mistakes in technote 27 “Known Anomalies in Unicode Character Names” ( https://unicode.org/notes/tn27/ ), with remarks such as “U+034F COMBINING GRAPHEME JOINER The name does not describe the function of this character. Despite its name, it does not join graphemes” “The use of the spelling lamda derives from ISO 10646. This does not mean that it is more correct than lambda, merely that the…

I’ve heard Greeks insist that lamda is indeed correct (as a non-misleading approximation of something like [lamða], not necessarily as an English spelling), so that part might have been a deliberate result of the ISO process.

(There’s also the name caron for the haček, apparently not used by anyone before the 80s; per the official FAQ:

Q: Why is the haček accent called “caron” in Unicode?

A: Nobody knows.)

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

#190

Post by tl »

TheNewAndy wrote: post #181
jrockway wrote: post #48

> Apple will offer more price points for apps. Today there are less than 100, but the company is committing to increase that to more than 500 options. I really hope they implemented this as an enum, so someone has to wade through: enum PricePoint { UNKNOWN = 0; NINTEY_NINE_CENTS = 1; ONE_DOLLAR = 2; TWENTY_DOLLARS = 3; NINETEY_EIGHT_CENTS = 4; DEPRECATED_NINETY_SEVEN_CENTS = 5; TEN_DOLLARS_PER_MONTH = 6; PORTUGAL_NAT…

There is some evidence of this - if you can log in to app store connect (need a developer account) there is this page: https://appstoreconnect.apple.com/apps/pricingmatrix/1539646... It shows the tiers from 0 (free) to 87 (USD 999). Then come the party tiers: 510, 530, 550, 560, 570, 580, 590 which are just repeats of the other tiers, probably for some good historical reason which I'm not aware of.

Just note, that link only works for you; if you have a developer account, you'll have to substitute the ten-digit number for one from your apps.
Post reply on HN