daughter asked me if the following impressions are correct

1) Google Translate is worse now
2) it's worse because it seems to flat out make up stuff
3) this must be because they're using so-called "generative AI", in a way their previous machine learning didn't
4) DeepL is also worse now for the same reason, but less so than Google Translate.

this is also my subjective impression of the state of things, but I have no idea how one would go about proving whether that's correct. it's not like we can get evidence of what's inside the proprietary black boxes

@elilla definitely agree to 1) and 2), probably 3) snd no clue about 4)
@elilla she’s probably right. We’d need to find a corpus of original and translated texts from the past, to compare if it is objectively worse. The reason would still be speculation, unless we find a Google employee who’s willing to spill.
@elilla DeepL has admitted to changing to an LLM. The original non-LLM model is still available... behind a paywall
@LilaHexe @elilla I don't think LLMs weren't in use before, though.
@navi @LilaHexe @elilla they were, they’ve been using LLMs for some time, TensorFlow is old as dirt
@LilaHexe @elilla do you have a link to this info? it's been a while since i've used deepl very frequently, i want to know if i should stop recommending it...
About DeepL language models

DeepL Translator uses language models to generate high-quality and accurate translations. On the web translator, in the desktop apps and via the API, you can choose between the classic and next-gen...

DeepL Help Center | How Can We Help You?
@alive @elilla "While the next-generation language model promises improved translation quality, the classic model still provides users with highly accurate and nuanced translations."

That's one way to say you know your new product is shit
@LilaHexe @alive one more strike for the increasingly widespread model of "LLM slop for the poors, quality stuff for those who can pay"
@elilla @LilaHexe @alive

I'm kinda interested in learning what they were using before the LLM, I thought DeepL was always a deep learning/AI based translator? (hence the name?)
@gracie @elilla @LilaHexe my understanding was that they had a custom neural network based model. unclear to me where the training data for that was, how much more traditional machine translation tech was mixed in, etc, but it worked quite well IMO
@alive @elilla @LilaHexe

yeah, DeepL was always better for me than other MTL software, sad to see it's going to shit now :(
@LilaHexe @elilla amazing how companies went from "you have to pay to use the LLM" to "you have to pay to not use the LLM" 💀
@elilla I've also got that sense with Google Translate lately
@empathicqubit @elilla seconding this. DeepL took a nosedive around 2023.
@elilla idk about deepl, but it seems to track for google translate
@elilla well, I'm glad to see that it's not just me and that DeepL has indeed gotten worse.

@elilla it was never very good to be fair… adequate at best, but awful if there is any slang or nonstandard sentence construction. Quality as always is very dependent on what language you use to and from, Indo-European languages usually mostly work between each other, but there’s often quirks.

It’s used an LLM for like a decade and a half now (people think LLMs are new… not even close to new). I think their newest tweaks have made it… better in some ways, worse in others? Mostly a wash.

It does seem way more mid at being a dictionary, which is what I used it for, and it sucks they seem to have gotten rid of the multiple suggestions feature.

Ah well.

@elilla yeah, google translate has been changing meanings entirely on me recently, like, I'll be using it to polish/grammar check an email or whatever, and it'll just change a sentence to a somewhat similar sounding sentence with an entirely different meaning.

For example, I was refining an email to a doctor for a prescription renewal (still the same quarter, so I can do it without showing up and save us all time), and it just totally butchered it into talking about first appointments.

If I didn't know the languages on both sides, that would be a real issue.

@mirahimage I feel like that's a good way of defining what's worse with Google Translation post-LLM era: it is now very dangerous to use it if you don't already know both languages. it always made errors, but now it makes something worse than errors (just flat out making shit up)

@elilla Something I've noticed lately to add to this list of Bads:

5) Translate results are more superficially fluent and plausible

that's the output smoothing from the LLM. earlier versions of translation would fail visibly (whether you knew the target language or not you could see syntax or word choices that didn't make sense) and informatively (you could tell something was off, and if you knew the target language even a little you'd probably see it). you could never count on translation results being suitable for copy-paste, and so—the inevitable corollary—you knew NOT TO COUNT ON THEM

now however translate results look "good," i.e. plausible, and unless you know the target language *better* than a little that veneer of plausibility effaces your ability to gut-check the results (and not just in the moment, but by way of steady erosion the more you engage with the software. in effect you're developing a muscle memory that tells you you CAN and SHOULD count on the results)

machine translation is every bit as unreliable as it always has been and *will* be: anyone who's actually done translation knows that it's not a solvable problem (nor in fact a "problem" at all in that compsci-ish sense), any more than "intelligence" is. but you can make it LOOK solved, and if you've bamboozled enough of your user base into playing along then who's to say it isn't?

meanwhile you've boosted your AI numbers and given yourself a whole nother category of deskilled labor you can show the axe to; and the money's very happy with you

@elilla UX development typically does everything it can to banish software failure from the user's mind; but if your software cannot in fact be used reliably (a different question from whether it's *worth* using) then making its lack of reliability VISIBLE is a crucial affordance, and removing or subverting that affordance is a form of fraud

@xangoh @elilla I almost exclusively use Google Translate only to translate between English and languages I already very vaguely know, so I can at least somewhat double check it.

Previously it used to be that if you translate from X to English but have Y selected as a source language, you'll just get the original untranslated text. But now I very often, when I forget to switch the language, get perfectly fine looking (but also utterly wrong) translations e.g. when I paste Italian text but forget to switch source language selector to Italian from German. It is ridiculous.