+Nevertheless, it is a fact _about contemporary English_ that "dog" means dog. If you thought this was bad for whatever reason, and you wanted to change that fact, you'd have to change the behavior of actually-existing English speakers. If you tried to stipulate on your Facebook wall that "blerble" should mean dog now, and all of your Facebook friends nodded in agreement at your clever argument _and then continued to call dogs "dogs" in their everyday life just like they always had_, then your language reform attempt would have, _in fact_, failed—even if the fact that it failed would be less obvious if you only looked at the Facebook thread full of people nodding in agreement.
+
+The inseparability of meaning from behavior-and-usage may be clearer if considered in a context other than that of natural language. Take computer programs. Sometimes programmers make bad design decisions. For example, in the C programming language, [it's standard to represent strings (textual data) in memory with a sequence of bytes ending in a zero (null) character](https://en.wikipedia.org/wiki/Null-terminated_string); the machine only knows where the string stops when it reaches the null at the end. This convention has a lot of disadvantages relative to the alternative of [prefixing the string data with the length](https://en.wikipedia.org/wiki/String_(computer_science)#Length-prefixed); a missing or misplaced null character could cause the machine to erroneously read or write data in adjacent memory, causing serious bugs or security vulnerabilities.
+
+Given the existence of strong arguments for the length-prefixed string convention, replacing old software that uses null-terminated strings with new software that uses length-prefixed strings, sounds like a good idea! But the thing is, you _do_ have to upgrade or replace the old software. If you _just_ start sending data in a new format to the old software that doesn't understand the new format, your code is not going to yield the expected results. It would be _convenient_ if you could just declare a new semantics for your existing data on your Facebook wall and be done, but that just doesn't work if you're still using the old software, which is programmed to behave according to the old data-interpretation convention. This continues to be true even if the convention you're trying to retire is very bad (like null-terminated strings), and if the old software is widely deployed and would be very expensive to systematically replace. The backwards-compatibility trap [is real and can't be defied away even if it's very unpleasant.](https://twitter.com/ESYudkowsky/status/1216799697907486720)
+
+Natural language faces a similar backwards-compatibility trap. The English language, as "software", is _already_ "deployed" [to 370 million brains as native speakers, and another 980 million second-language speakers](https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers#Top_languages_by_population). And among those hundreds of millions of speakers, there is _already_ a very firmly entrenched convention that _she_ refers to females and _he_ refers to males, such that if you say, "I met a stranger in the park; she was nice", the listener is going to assume the the stranger was female, even if you didn't say "The stranger was female" as a separate sentence. If the listener later gets the chance to meet the stranger and the stranger turns out to be male, the listener is going to be _surprised_: your pronoun choice induced them to [mis-anticipate their experiences](https://www.lesswrong.com/posts/a7n8GdKiAZRX86T5A/making-beliefs-pay-rent-in-anticipated-experiences).
+
+Bad language design? I mean, maybe! You could argue that! You could probably get a lot of Likes on Facebook arguing that! But if 370 million native English speakers _including you and virtually everyone who Liked your post_ are going to _continue_ automatically noticing what sex people are and using the corresponding pronouns without consciously thinking about it (in accordance with the "default for those-who-haven't-asked" clause of your reform proposal), then the criticism seems kind of idle!
+
+The "default for those-who-haven't-asked [going] by gamete size" part of Yudkowsky's proposal is _trying_ to deal with the backwards-compatibility problem by being backwards-compatible—recommending the same behavior in the vast majority of cases—but in doing so, it fails to accomplish its stated purpose of de-gendering the language.
+
+To _actually_ de-gender English while keeping _she_ and _he_ (as contrasted to jumping to universal singular _they_, or _ve_), you'd need to _actually_ shatter the correlation between pronouns and sex/gender, such that a person's pronouns _were_ just an arbitrary extra piece of data that you needed to remember in the same way you have to remember people's names. But as far as I can tell, _no one_ wants this. When's the last time you heard someone you heard someone request pronouns for _non_-gender-related reasons? ("My pronouns are she/her—but note, that's _just_ because I prefer the aesthetics of how the pronouns sound; I'm _not_ in any way claiming that you should believe that I'm female, which isn't true.") Me neither.
+
+
+
+[TODO—
+ * Given that sex-category information is _in fact_ being transfered, the "Pronouns are Ryphnol" lady has a point
+ * To relate this to Yudkowsky's specialty And preferred pronouns have the same function as the typographic attacks in the multimodal-neurons paper
+ * the people aligning language models should understand this
+]