I agree; many projects (both FOSS and non-FOSS) lack sufficient documentation. However, this is the case whether or not it is English; it is another issue.

More simplified English might be a good idea. There is what is called Simplified Technical English, but that seems to be for aerospace, and perhaps it could be adapted for computer documentation, too.

I am willing to accept contributions of documentation in any language whether English or otherwise for my projects, although I am only writing in English myself, others can write in other languages if they want to do. (However, I generally have no intention to support commands and status messages etc in languages other than English, nor in character encodings other than ASCII.)

For names of stuff (and comments) in the source code of the program itself, I do not consider it too important to write in other languages, although people can try to do that if they want to do. At least for my own projects though, I intend to limit the source code to ASCII.

> More simplified English might be a good idea. There is what is called Simplified Technical English, but that seems to be for aerospace, and perhaps it could be adapted for computer documentation, too.

I'm happy that you think that the idea in the article is good.

I didn't know about the "Simplified Technical English" it seems interesting.

I reply below to some points but only to share better my point of view I tried to wrote in the article.

> I'm not sure if more linguistic diversity will help FLOSS.

I think linguistic diversity in FLOSS means a more accessible FLOSS world to people that not speak English.

> For countries with more English speakers (e.g. most European countries) I don't think translations provided to developers will prove beneficial.

But here in Europe (I'm from Italy) not all country have the same level English skills. I also wrote the article thinking to the whole World with so meny country with a low level of instruction.

> The language-mastery issue is real, especially for very young people, but I'm not sure if "forcing" people isn't the better call.

I don't think in the article I wrote about forcing people.

> The suggestions for more simplified English in the article seem like good ideas to me.

Thanks, I'm happy you found the idea good.

Not explicitly, but it's essentially the consequence of not increasing language diversity in FLOSS. If you want to get involved, learn English. That's the "forcing" they were talking about.

Thanks for summarizing this concept. It's sad but it's true.

Seriously. American kids can start to learn to program at age 6. Non-English-speaking kids can do so once they're old enough to know English.

Who do you think will have the edge?

Plus, there's a ton of coding in all fields. Learning english to be a programmer is perhaps fine, but to be able to analyze data in seemingly EVERY field of endeavor? Or automate basic routine tasks?

The language issue is an issue, and one worth solving.

> Seriously. American kids can start to learn to program at age 6. Non-English-speaking kids can do so once they're old enough to know English.

I don't think that follows at all. Non-English-speaking kids can also start to learn programming at any arbitrary age. What they need to learn for that is a programming language, not English.

Sure, most programming languages are subsets of English -- but extremely limited subsets. And the meanings of the words in them are (often radically) different from the original meaning of the same word in English; I suspect English-speaking learners have only a tiny initial advantage of the words being similar, but in effect have to learn them as if they were from a foreign language anyway.

I agree with that, but what I've explained in the article is that if you don't know English is harder to access English-only documentation, resources, etc...

This can be changed by the community to be more inclusive, especially for newcomers, kids, ...

Yes, I do think we should have translations for everything.

We should have infrastructure to view code in multiple languages. Blockly games, Hour-of-Code, and parts of Microsoft MakeCode do this already. You flip a button and "on start" becomes "nar programmet starter" or "all'avvio."

Programming is easy, since code is structured, and it's easy to parse what's a variable and what's a function call. The translation problem, outside of comments and documentation, is a lot easier than natural language.

Furthermore, a lot of this stuff generalizes since the same words are used so often. Once there's a translation for "page_loaded," you can use that across many platforms.

I should be able to select a drop-down, and have the same for any program I can find on github or gitlab, and edit code in my native language.

It's a (huge) one-time investment. But once that investment is made, sustaining is cheap. A lot of translation works well enough automated (through Google or Amazon translate), and what doesn't translate well can be cleaned up by crowdsourcing. Google Translated comments are usually actually good enough.

Conversely, in the linguistically fragmented scenario, you're SOL, as it's pretty unreasonable to learn N different languages.

Multilingualism is a barrier in human development that should be overcome, not something to celebrate or protect.