Earlier quoted context omitted.
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. )
Apple agrees to settle potential class action suit by U.S. developers
221–230 of 259 posts
Re: Apple agrees to settle potential class action suit by U.S. developers
#222>Apple agrees to make sure the search results in the App Store are based on objective criteria. I cant help but laughed when I was reading it. What were they doing before that? I thought the most important part was the next bit, >The settlement, which must be approved by Judge Yvonne Gonzalez Rogers, comes as Apple is awaiting a ruling in a separate lawsuit, brought by Fortnite developer Epic Games, which seeks to fo…
> I cant help but laughed when I was reading it. What were they doing before that?
I assume that's referring to the fact that previously, they occasionally hard-coded certain search terms to show Apple app results before third-party apps, even if the search term was an exact match. [1]
And that "objective" search results means no more hard-coding of exceptions like this to give "partiality" to a particular company or app.
Re: Apple agrees to settle potential class action suit by U.S. developers
#223Earlier 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.....
You may notice that a lot of the code in Allegro spells 'palette' as 'pallete'. This is because the headers from my old Mark Williams compiler on the Atari spelt it with two l's, so that is what I'm used to.Re: Apple agrees to settle potential class action suit by U.S. developers
#224Earlier quoted context omitted.
Developers are also not allowed to link to account management on a webpage if they signed up via a website, which contributes to lots of user confusion when it comes to cancellation of a subscription for instance.
I think this is exactly what is being changed here? Now you can link away to a web portal with your account and alternative payment options. Correct me if I'm wrong.
Re: Apple agrees to settle potential class action suit by U.S. developers
#225Earlier quoted context omitted.
At this point I think it may be question whether the problem lies with English itself. Such an error prone language.
You don't know the half of it. Many contemporary and common words are the results of misspellings. “a nickname” was originally “an ekename” (eke being an old English word meaning also) conversely, “an apron” was originally “a napron.” English is a weird agglomeration of different languages, with things like the application of French-style plurals (-s) to Anglo-Saxon words (but not always, cf. ox -> oxen) and a genera…
Re: Apple agrees to settle potential class action suit by U.S. developers
#226> 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.
Re: Apple agrees to settle potential class action suit by U.S. developers
#227Earlier 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?
Re: Apple agrees to settle potential class action suit by U.S. developers
#228Re: Apple agrees to settle potential class action suit by U.S. developers
#229Earlier quoted context omitted.
At this point, I don't think it's an economic calculation anymore, if it ever was. I think it's moreso that Apple genuinely believes that third parties shouldn't have access to their platforms without prior review. Everything else has an explanation from that: - We need to monopolize control over who can publish software for our platforms, so we can enforce our security guidelines. (This includes banning third-party…
>- Thus, we can't have third-party billing, because that would let developers evade payment for our software review. Except for having to buy a Mac to do development in the first place. And the developer registration yearly fee.
Re: Apple agrees to settle potential class action suit by U.S. developers
#230Earlier 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...
I thought it was supposed to be REEFERER.