Like many natural languages, computer languages are often much easier to read than to write. This is true for me, so I assume it is true for everyone (correct me if I am wrong).
Speaking from the perspective of an "old man", I have been exposed to many, many languages, and have even maintained code written in many. I have had the "pleasure" of first-hand experience in some of the "foundational" languages, like C (on microcontrollers, mostly), and even assembler. I have database, and object oriented experience, etc.
Notice, though, that in each case I am mostly reviewing the algorithm, and assumptions that are being made, and not the style, or other aspects I am not familiar with. Review what you know, not what you don't know. If you can spot an algorithm that is inefficient, it does not matter what language it is in. If you can spot an edge-case that should be considered, it does not matter about the language.
The language is only a part of the question to be reviewed, and, on Code Review, you can review any, and all aspects of the code, so you can review what the code does, how the functionality is implemented logically, as well as how that logic is implemented in the language of choice.
Just so long as you can spot the logic, and determine how that logic solves the problem, you're fine.
Leave the language-specific parts for people more versed in the language.