The general population of the world is rather more likely to speak Spanish than English. If that’s your line, then the rest of the text should be translated to Spanish as well. Or perhaps to Chinese.
You’re missing the point. I would not have commented about a Spanish article, but translated it.
But it is an English article with a couple of lines of Spanish in it and I don’t see a good reason for that except that I think the author reused their code verbatim instead of adjusting it. Furthermore I get the gist of the Spanish parts, but it’s code, or inline docs - so I assume every character/word is important.
I think this would have been a lot more understandable by translating the ~10 lines of docs in the example code to English to match the article.
We’re in a multi lingual world now. And fortunately machine translation is pretty good when you know you’re interested in the document.
We have the tools to read black text on black background and yet the general population would agree that it is not optimal.
The general population of the world is rather more likely to speak Spanish than English. If that’s your line, then the rest of the text should be translated to Spanish as well. Or perhaps to Chinese.
You’re missing the point. I would not have commented about a Spanish article, but translated it.
But it is an English article with a couple of lines of Spanish in it and I don’t see a good reason for that except that I think the author reused their code verbatim instead of adjusting it. Furthermore I get the gist of the Spanish parts, but it’s code, or inline docs - so I assume every character/word is important.
I agree somewhat, but I have to say that this almost sounds like a setup to make fun of incomprehensible parts of Perl code…
What a coincidence: the author of this Git article is JJ ;-)