> I am also curious about the mentioning of Indian males in the text alongside native American women, with the chart excluding Indian males, this is also somewhat confusing.
I also found this confusing at first, but I realized that the author uses "American Indian" and "Native American" interchangeably. In the chart, this group is labeled "Native American Men".
I too found it confusing when people started using "crypto" to be short for "cryptocurrency" (and later, all blockchain-related things) rather than "cryptography". However, that ship has sailed and as Moxie Marlinspike points out in his NFTs post [0], that's now a Pepperidge Farm Remembers meme. I've come to accept it as a shift in usage and using the older meaning of crypto will just result in miscommunication, like in this thread.
So, to answer your question: no, those things don't depend on blockchain, but they're also not "crypto", according to the current usage of the word.
In Germany, you can also collect unemployment benefits after you've quit or been fired with cause. However, in those cases there is a waiting period of 12 weeks before you can start collecting benefits. If you have been laid off for reasons not related to your performance, including for long-term illness, you can start collecting benefits immediately.
While I agree with you in general, a surprising number of grammatical features that make many other languages difficult to learn are missing in Indonesian. Some examples:
No grammatical gender
No plural forms of nouns
No grammatical case
No verb conjugations
No verb tenses
In addition, written Indonesian uses the Latin alphabet and has a very consistent phonemic orthography.
Of course, it also has some more complicated features, like formal and informal pronouns. But it still seems fair to me to say that it is grammatically simpler than many (most?) other spoken languages.
I don't think that is fair to say. There are lots of other languages that lack most/all of these features (e.g. Mandarin has no gender, limited number marking, no case marking, lack of inflections). Indonesian is not unique in that regard.
Indonesian verbs lack the tense, number and person agreement marking that is commonly found in European languages, but they have a lot of derivational morphology including complex voice and valency operations (Austronesian alignment[0], causatives, applicatives etc.)
Indonesian also has noun classifiers like Mandarin which have to be memorised like grammatical genders.
Yup, typically what a native Indonesian would say about how easy their language is. But foreigners are often tripped with other aspects of the grammar, which the native take for granted, such as those tikwidd mentions: noun classifiers, morphological derivation, a high number of prefixes/suffixes/infixes and their combination, lack of cue on how to pronounce the different "e" vowels, etc.
> US Copyright defaults to the author, it is only with employee contracts/agreements that one can forego the default and assign to the company.
I'm pretty sure this is not true. In fact, it's the opposite of how it actually works. There's an explicit exception in the Copyright Act for a "work made for hire". If you're creating a opyrighted work for an employer, the employer is always the author of the work at the moment of inception.
A somewhat similar question: what do you do with frontend assets? If you have JS/CSS/image files with a cache-busting URL, and you have different versions on different servers, you can run into problems.
For example, if most of your web servers are running version 1 and you're in the middle of rolling out version 2. A page request goes to one of the web servers with version 2, which returns HTML containing links to assets with the version 2 cache-busting URLs. The browser requests those assets, perhaps through the CDN, but the load balancer sends the requests to a web server still running version 1, where the assets don't exist yet. This means the browser will get a 404 error.
What are the best options for dealing with this problem?
Not sure that this is the best answer, but seems like a good use of feature flags. If the flag points to the old state, serve the old assets. If it points to the new state, serve the new assets. So make a deploy with both assets, deploy everywhere, then flip the flag.
A bit unsatisfying because it probably isn't always easy the include both assets.
Another idea (not sure if a good one) would be having the load balancers pin a certain session to a certain backend machine. Seems like this would make it better without fixing it, though: that session will still need to switch to a different set of assets when "their" server is deployed.
The underlying problem is the use of a naive cache buster which would cause the old server to reply one way and the new one another. For both the people who want the old asset and the new asset.
If instead of being something the web server throws away before replying, the version number actually caused different assets to be returned, then you'd not have this problem.
One pattern is to separate out assets into a different package that is deployed to a separate host group and have your clients request a different host name, or have your load balancers use a path match to use those servers for those requests.
Another is to push asset updates first to all hosts. All hosts, even without code update, will now be able to respond for the new assets.
Another is to use a local cache plus some backend service or database to serve the assets from the web servers - again, all hosts will now respond correctly for the old assets and the new.
>By 1982, an estimated 621,000 home computers were in American households, at an average sales price of US$530.
In a country of 220 million people. If we assume about 4 people could access a single computer, then 1,1% of population had access.
So it seems commercials of Apple II and TRS-80 was the thing that compelled women to stay out of the field. Or alternatively getting your hands on dads TRS-80 was incredibly compelling experience to almost every boy out there.
I also found this confusing at first, but I realized that the author uses "American Indian" and "Native American" interchangeably. In the chart, this group is labeled "Native American Men".