151–160 of 188 posts
Earlier quoted context omitted.
Looks like this constant should be parsed as: ElderCousin && (MothersSiblingsDaughter || FathersSistersDaughter)
Mother's Sibling's Daughter or Father's Sister's Daughter. FYI, Mother's Sibling is 舅舅 (Mother's Brothers) or 姨 (Mother's Sisters), and Father's Sister is 姑姑.
Earlier quoted context omitted.
Why on earth would someone do bug fixes for free for a corporation that has cash reserves of $250 billion but is too stingy to pay for quality control?
Because otherwise thousands of developers will have to see that typo for the next ten years.
I can see why this is needed. English has very broad words for relatives like "grandfather" or "aunt". Most languages have more specific words, especially Chinese where there are separate words for fathers or mothers side, older or younger and sibling or siblings spouse. You also often use these relation words rather than their names when referring to a relatives. If this code was in Chinese, they would all be short…
The original English version had a passage where it was unclear (on purpose) which grandmother was being referred to (it later turned out to be the one you didn't expect). However, with Swedish having no generic word for grandmother (only mormor and farmor), this nuance was lost in the translation.
Earlier quoted context omitted.
They could have used Pinyin. Even people who don’t speak Chinese and have to look it up would have an easier time understanding it than trying to parse this identifier.
And then every time you re-read the code you have to look it up to understand 1/ what the hell is even this and 2/ is it the right one at the right place.
Earlier quoted context omitted.
I'm assuming those Mandarin characters comprise the word for that relationship? I was wondering why this existed and I thought maybe they were adding the Hindi words for specific relatives (there's many, I assume the same is true for Mandarin).
Mandarin is a spoken language. The characters are "Simplified Chinese" in this case. The characters will sound different read in different languages. e.g. the two Traditional Chinese characters 東京 translate roughly to "Eastern Capital" and are read dōngjīng, while they are also valid Japanese Kanji where they have the same meaning and are read as Tokyo. (Yes, the name of the capital of Japan.) Interestingly, Běijīng…
“There are only two hard things in Computer Science: cache invalidation and naming things.” [1] [1] https://martinfowler.com/bliki/TwoHardThings.html
Anybody care to introduce me to this? Why does it have to be father's sister but mother's sibling? And how does elder and younger cousins behave differently?
This one seems to come from chinese * in many EA and SEA culture, there's a difference made based on the age differential aka different term of address to people older than you v younger than you, also gender * chinese (and likely others) also make a difference between patrilineal relationships and matrilineal, so there's a term of address for people related through the father's brother (and thus sharing your family…
At first glance this looked like a code smell, but after some reflection I can't think of a cleaner, more readable way to uniquely identify each possible relationship -- especially in a strongly-typed language with an IDE. Here's the full list: https://developer.apple.com/documentation/contacts/contacts_...
Here's the likely explanation for these: https://en.wikipedia.org/wiki/Chinese_kinship#Common_extende...
Earlier quoted context omitted.
Because otherwise thousands of developers will have to see that typo for the next ten years.
But by fixing it yourself, aren't you effectively training the corporation to stay sloppy? Sure, this bug is fixed right now. But a year down the road, when the staff count for quality assurance gets renegotiated, the position to deliver quality out of the box gets weakened, resulting in even more bugs of this kind.
Are you saying that no-one should report anything because it encourages them to let bugs slide into production?
Earlier quoted context omitted.
But by fixing it yourself, aren't you effectively training the corporation to stay sloppy? Sure, this bug is fixed right now. But a year down the road, when the staff count for quality assurance gets renegotiated, the position to deliver quality out of the box gets weakened, resulting in even more bugs of this kind.
This is slightly absurd. It's reporting a very minor bug, not offering to implement a whole feature. Are you saying that no-one should report anything because it encourages them to let bugs slide into production?
No, of course not :) That would indeed be absurd. What I meant was this particular case. Apple of all companies is by no means incapable of hiring people to deliver quality. They make billions upon billions by avoiding taxes[0] and shifting production to deleloping countries [1]. If a company like this learns that it can externalize QA even more, they will do so. We are not talking about social contract like situtions here, this isn't open source software.
[0] = https://itep.org/fact-sheet-apple-and-tax-avoidance/
[1] = https://www.theverge.com/2019/6/28/19102703/apple-mac-pro-ch...