← Back to context

Comment by yde_java

5 days ago

Being proud of your culture including your language and exercising it, at the risk of readers not understanding everything immediately, is not racism. In the worst case, a non-British gets curious about one expression or the other and looks it up. That's engagement.

It's funny, and perhaps not entirely unwarranted, that "racism" pops up here?

As a Black American, I find the author's idea extremely interesting and naturally began to wonder -- what might this idea (in code?) look like for us?

Owing to history and whatnot, the role "Black American English" might play is of course very much a moving target, but it's interesting to think about.

  • As a writer and amateur linguist I can always spot the people who don’t understand how AAVE works because they seem to think that it’s just “bad grammar” and don’t realize that it does in fact have its own grammatical rules. One that’s not exclusive to AAVE, but is common across most informal spoken English in the US (maybe beyond—I know there’s at least one Genesis song that uses this which suggests it may exist in informal British spoken grammar), is the use of the oblique case when a subject has two or more elements joined by and: “Steve and him went to the store” insted of “He and Steve went to the store.” (Ordering is also subject to different ordering with formal English dictating that the first person pronoun comes last, but informal English putting it first: “Me and him” vs “He and I.”

    The other thing I find interesting is that formal English has eschewed the double negative as an intensifier while most (all?) other Indo-European languages employ it. Compare Spanish “No veo nadie” (literally ”I don’t see nobody“ which is the informal English formulation) to English “I don’t see anybody.”

  • Is there an internationally agreed upon standard for designating AAV? I suppose it's a large and influential enough dialect it wouldn't hurt to have one

    • The main people who'd want such a thing would be linguists, so that they can label samples.

      The non-prestige dialects of a language don't usually attract official interest, not least because officially the people who understand that dialect could also understand a prestige variant. Scousers may not talk like King Charles among themselves, but if he speaks they're not confused about what the King is saying even if they wouldn't use those words or say them that way.

      This might get sketchier for Chinese topolects where the official government policy is that China has a single language, "Standard Chinese" but, those topolects sure do seem like different languages if you didn't know about the policy. However AAV is nowhere close to that, I can't imagine that anybody who uses AAV normally watches "Last Week Tonight" and goes "That guy is speaking a completely unrecognisable language, are there subtitles?".

      11 replies →

    • Not to my knowledge, and I imagine even trying to do this would stir up.. a lot.

      The more I think about it, the more difficult it seems. Not that it shouldn't be done, but wow.

  • As one example I have seen plenty of Code read Color redColour = .....

    That is how it often manifests, the bits the Brits get to choose is in their own language and spelling.

Nobody said it was.

  • The article strongly implies it is a response to a comment complaining the blog is not inclusive because it uses British English.

    There is a constant American assumption that their language and culture is the norm and we should all adjust our language to fit their definitions and culture. I intend to keep eating faggots, having a master branch in git, etc.

    •     > There is a constant American assumption that their language and culture is the norm
      

      You write it like it is a moral flaw in American culture. This cultural phenom isn't special to the United States. In my personal experience, any country with a large population suffers from the same: Russia, Brazil, Indonesia, India, China, etc.

          > having a master branch in git
      

      This is a weird cultural battle to pick. In the 2010s, when renaming the git master branch was at its cultural zeitgeist, none of the Americans that I worked with did the rename. It was always someone not from the US who would raise the issue on a team call. It happened so many times that I asked a few of them why they did it. Almost all of them told the same rough story: They say a "nerd news story" about the trend, then did a little bit of reading on Wiki to learn about the cruel history of slavery in the United States. Motivated by this, they decided to do the rename. All in all, pretty wholesome stuff. Never once was it some weird social justice warrior type of bullcrap. But anyway, you do you: Keep rockin' the "master" branch in git.

    • "There is a constant American assumption that their language and culture is the norm"

      This is now far more than an American assumption. I have seen younger continental Europeans bristle at UK English because they grew up in a world of social media that is converging on usage that is closer to US English.

      1 reply →

    • When I read "inclusive", my mind jumped to accessibility, in that colloquialisms can be difficult to understand for a subset of people with autism (and other conditions), and also that they translate poorly when run through a translator, for those that do not speak English at all.

    • > I intend to keep eating

      Wait, isn't that a cigarette? Why would you eat it?

      edit: nevermind, it's actually meatballs, the short version is for cigarettes