As a German native speaker, it's surprisingly hard to read the code examples. Seems like all common concepts of programming languages like access modifiers, types etc. are hardwired to their English terms in my brain.
Rost also did do extra work to have maximally diverging naming.
- struktur could have been strukt
- umstz could have been impl as in Implementierung was added to the German language
- nutz would be a more realistic replacements of use
- Mutieren is a German word so mut would stay mut
- unsafe is better translated as unsicher, not gefährlich which is dangerous
- hinein is a translation for into but .into() a short for "convert into", which in German is "konvertiere zu" so `.zu()`, similar "convert ... from .." would be roughly "aus ... erstelle ..." so `.aus()`.
- etc.
in general authors do choose language keywords, syntax and acronyms so that they flow/read reasonable nicely and that isn't true here in many ways. If we don't just try to translate by word but by what we mean with the word in given context then verhalten would be a better choice for trait and you can definieren (define) behavior so `impl Behavior for Thing` become `def Verhalten für Ding`. Similar static wouldn't become statisch but instead global.
When I first read the examples, besides my laughter, I felt a similar disconnect im the semantics of the chosen German words. Thank you for you suggestions, I agree with all of them, they are better indeed IMHO.
I've never been able to even use localized UIs on anything that goes on my computers and my phone. My native Romanian looks either foreign or silly when it's on the "File" menu.
It's probably what you got used to when you first learned it though.
Because I am also slow at reading math / the theoretical part of IT in English because I learned it ... in Romanian.
Edit: to the point that I didn't remember the "theoretical part of IT" is "Computer Science" when posting in a hurry :)
With me it goes so far that I switch everything that can be switched (e.g. Android on my phone) to English. It's not just the terms, it's also the frequent translation errors. One "oldie but goodie" example is a Windows utility (I think it was Registry Editor, but not sure anymore) that translated "key" with "Taste" - which means key on a keyboard, not key as in a thing that opens doors or allows you to uniquely identify a bit of data, that would have been "Schlüssel".
I do the same thing. When helping friends with their computer problems, having to translate words in a menu is such a hassle, especially when the translations aren't obvious.
When it turns out they were using a different version and didn't have that option, we still had to figure out what translates to what – if the option even is there at all.
As an English native speaker, that makes sense to me. When I read code, I don’t really think of keywords as being related to the English word that inspired them; they’re just their own distinct symbol to my brain.
