I'm writing this in English.
-
I'm writing this in English.
Not because English is my first language—it isn't. I'm writing this in English because if I wrote it in Korean, the people I'm addressing would run it through an outdated translator, misread it, and respond to something I never said. The responsibility for that mistranslation would fall on me. It always does.
This is the thing Eugen Rochko's post misses, despite its good intentions.
@Gargron@mastodon.social argues that LLMs are no substitute for human translators, and that people who think otherwise don't actually rely on translation. He's right about some of this. A machine-translated novel is not the same as one rendered by a skilled human translator. But the argument rests on a premise that only makes sense from a certain position: that translation is primarily about quality, about the aesthetic experience of reading literature in another language.
For many of us, translation is first about access.
The professional translation market doesn't scale to cover everything. It never has. What gets translated—and into which languages—follows the logic of cultural hegemony. Works from dominant Western languages flow outward, translated into everything. Works from East Asian languages trickle in, selectively, slowly, on someone else's schedule. The asymmetry isn't incidental; it's structural.
@Gargron@mastodon.social notes, fairly, that machine translation existed decades before LLMs. But this is only half the story, and which half matters depends entirely on which languages you're talking about. European language pairs were reasonably serviceable with older tools. Korean–English, Japanese–English, Chinese–English? Genuinely usable translation for these pairs arrived with the LLM era. Treating “machine translation” as a monolithic technology with a uniform history erases the experience of everyone whose language sits far from the Indo-European center.
There's also something uncomfortable in the framing of the button-press thought experiment: “I would erase LLMs even if it took machine translation with it.” For someone whose language has always been peripheral, that button looks very different. It's not an abstract philosophical position; it's a statement about whose access to information is expendable.
I want to be clear: none of this is an argument that LLMs are good, or that the harms @Gargron@mastodon.social describes aren't real. They are. But a critique of AI doesn't become more universal by ignoring whose languages have always been on the margins. If anything, a serious critique of AI's political economy should be more attentive to those asymmetries, not less.
The fact that I'm writing this in English, carefully, so it won't be misread—that's not incidental to my argument. That is my argument.
-
@hongminhee Criticisms of Anglophonic hegemony are similar to (and inseparable from) criticisms of capitalism.
In many cases, systems people put in place to mitigate capitalism's harms inadvertently strengthen capitalism's grip (e.g. tax credits for low paid workers allow them to be paid even less).
Similarly, lowering the bar for communication in English, as you describe, makes it ever less likely that we'll ever start treating non English speakers as first class citizens.
-
@hongminhee Criticisms of Anglophonic hegemony are similar to (and inseparable from) criticisms of capitalism.
In many cases, systems people put in place to mitigate capitalism's harms inadvertently strengthen capitalism's grip (e.g. tax credits for low paid workers allow them to be paid even less).
Similarly, lowering the bar for communication in English, as you describe, makes it ever less likely that we'll ever start treating non English speakers as first class citizens.
@krans@mastodon.me.uk The analogy is structurally interesting, but I think it breaks down at a crucial point.
With tax credits, the argument is that the subsidy lets employers off the hook—pressure that would otherwise force wages up gets absorbed by the state instead. The discomfort falls on capital, or at least that's the intent. But when you apply the same logic to language access, the discomfort doesn't fall on the Anglophone center. It falls on the people who were already excluded. The implicit suggestion becomes: non-English speakers should communicate less fluently, so that English speakers are eventually pressured into… what, exactly? Learning Korean? There's no mechanism there.
The deeper problem is that “lowering the bar for communication in English” is not the same thing as accepting English hegemony as permanent. I use these tools to participate in a conversation that would otherwise exclude me. That's not capitulation—it's the same logic as using a wheelchair ramp. You don't refuse the ramp because its existence lets architects keep building stairs.
The structural critique of hegemony is real and I share it. But it shouldn't cash out as advice to the marginalized to make themselves less legible. That's a cost I'm not willing to ask people to pay on behalf of a structural shift that may never come.
-
@hongminhee My employer is perfectly capable of affording to translate our product manuals into Korean professionally — I'm here in Korea right now supporting a *massive* customer.
Instead our official policy is that Korean users will be fed LLM slop that our tech writers won't even attempt to read and validate.
That's exclusion and condescension packaged as providing access.
-
@hongminhee My employer is perfectly capable of affording to translate our product manuals into Korean professionally — I'm here in Korea right now supporting a *massive* customer.
Instead our official policy is that Korean users will be fed LLM slop that our tech writers won't even attempt to read and validate.
That's exclusion and condescension packaged as providing access.
@krans@mastodon.me.uk That's a real and legitimate grievance, but it's a different argument from the one we were having.
Your employer using LLM translation to cut costs on documentation for a massive Korean customer (while having the resources to do it properly) is a decision made by someone with power, to save money, at the expense of Korean users. That's worth being angry about.
But I'm an individual trying to participate in a public conversation. I can't hire a personal interpreter every time I want to respond to a post. The choice I actually face is: use available tools, or stay silent. Those aren't the same situation, and the same tool can mean very different things depending on who's holding it and why.
If anything, your example reinforces the point. The problem isn't the tool, but it's who gets to decide when it's “good enough.”