131–140 of 259 posts
Earlier quoted context omitted.
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...
Early header compression.
>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…
Either I am misreading this part of your comment, or you may have overlooked this paragraph:
> With the exception of the fund for small developers, the rest of the changes are being made globally.
>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…
> 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…
Does the settlement allow for alternative payment methods to be cheaper?
Earlier quoted context omitted.
Complete with spelling errors, semicolons in place of commas, shouting snake case, and unnecessary explicit numbering. Definitely enterprise-grade.
The real enterprise case is when additions are made for things that aren’t even pricing
> 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.
Earlier quoted context omitted.
I'll just leave this here for you: https://datatracker.ietf.org/doc/html/rfc7231#section-5.5.2
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.
“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 spelling without the 'b' is the one used in the formal character names”
“A spelling error: "brakcet" should be "bracket". A formal alias correcting this error has been defined”
Earlier quoted context omitted.
Complete with spelling errors, semicolons in place of commas, shouting snake case, and unnecessary explicit numbering. Definitely enterprise-grade.
The real enterprise case is when additions are made for things that aren’t even pricing
enum PricePoint {
//all the 500+ price points defined above...
REGULAR_PRICE = 1023;
PROMO1_PRICE = 1047552;
PROMO2_PRICE = 1072693248;
AUTOHINT_ROUND_99 = 1073741824;
AUTOHINT_BUYING_POWER = 2147483648;
}