But arguably, as long as the compiler supports unicode, it shouldn't matter that much what language the keywords are in. There are other more important issues impacting how easy it is to program in non-English languages:
availability of documentation and tutorials
English comments and API names in common libraries, especially the standard library
tooling for handling unicode, especially BiDi (which is part of why Arabic is especially tricky) - Vim, for instance, has had an open issue about this for almost a decade: https://github.com/vim/vim/issues/204
it shouldn't matter that much what language the keywords are in
Another problem is that the grammars of many well-supported programming languages also mirror English/Romance language grammars. Unfortunately, dealing with that is more than just a matter of swapping out keywords.
EDIT: I may have been unclear; I wasn't trying to imply that this problem is greater than or even equal to the lack of documentation, tutorials, libraries, etc. Just that it's another issue, aside from the individual words themselves, which is often overlooked by monolingual people.
What do you mean by that?
I'm no linguist, but I have some Japanese language ability, and Japanese seems to be pretty different, grammatically, from English, so I'll draw on it for examples. I also had a quick look at some Japanese-centric programming languages created by native speakers and found that they were even more different than I'd imagined.
Here's a first example, from an actual language, "Nadeshiko". In pseudo-code, many of us would be used a statement like the following:
print "Hello"
Here's a similar statement in Nadeshiko, taken from an official tutorial:
「こんにちは」と表示
A naive translation of the individual words (taking some liberties with English) might be:
"Hello" of displayment
I know, I know, "displayment" isn't a real English word, but I wanted to make it clear that the function call here isn't even dressed up as a verb, but a noun (of a type which is often used in verb phrases... it's all very different from English, which is my point). And with a more English-like word order, it would actually be:
displayment of "Hello"
Here's another code sample from the same tutorial:
「音が出ます！！」と表示。
1秒待つ。
「プログラミングは面白い」と話す。
And another naive translation:
"Sound comes out!!" of displayment.
1 second wait.
"Programming is interesting" of speak.
And finally, in a more English-like grammar:
displayment of "Sound comes out!!."
wait 1 second.
speak of "Programming is interesting".
And here's a for...in loop, this time from my own imagination:
for foo in bar { }
Becomes:
バーのフーで { }
Naively:
Bar's Foo with { }
More English-y:
with foo of bar { }
You may have noticed that in all of these examples, the "Japanese" code has little whitespace. Natural written Japanese language doesn't use spaces, and it makes sense that a coding grammar devised by native speakers wouldn't need any either.
Now, do these differences affect the computer's ability to compile/interpret and run the code? No, not at all. Is the imposition of English-like grammar onto popular programming languages an insurmountable barrier to entry for people who aren't native English speakers? Obviously not, as plenty of people around the world already use these languages. But I think that it's an interesting point, worth considering, in a community where people engage in holy wars over the superiority or inferiority of various programming languages which have more in common than many widely-spoken natural languages.
I'm trying to think of examples of this, and I actually don't know that this is true. Here are the examples I can think of:
Arguably object-oriented .method() syntax is similar to "subject-verb" order, but we also have function(self, ...) which is the reverse of that.
for foo in bar is used in a few languages (or sometimes foreach). But many languages use a totally non-English construct, such as for i = 0; i < limit; i++ or for (auto foo : bar).
What else is there?
Drawing on Japanese, which is the only non-English language I have significant experience with, object.method(parameter) would feel more natural as object.(parameter)method, possibly even replacing the period separator with a Japanese grammatical construct (with no equivalent in English) that really suits this use case. Even the alternative function(self, parameter, ...) would mesh better with natural Japanese grammar as (self、parameter、〜)function. The majority of human languages have sentences which run Subject-Verb-Object, but a handful which includes Japanese run in the order Subject-Object-Verb.
I gave an example of an alternative for...in loop in another comment here, so I won't rehash it here. But following the general flow of Japanese grammar, that for at the beginning of the statement would feel much more natural as a で (or "with") at the end of the statement, since particles (somewhat similar to prepositions in English) go after the noun that they indicate, rather than before. And since semicolons don't exist in Japanese either, even they might be replaced with a particle like "と".
There aren't any big problems here, but a plethora of little things that can slowly add up.
There are a fair number of them: https://en.m.wikipedia.org/wiki/Non-English-based_programming_languages
But arguably, as long as the compiler supports unicode, it shouldn't matter that much what language the keywords are in. There are other more important issues impacting how easy it is to program in non-English languages:
Another problem is that the grammars of many well-supported programming languages also mirror English/Romance language grammars. Unfortunately, dealing with that is more than just a matter of swapping out keywords.
EDIT: I may have been unclear; I wasn't trying to imply that this problem is greater than or even equal to the lack of documentation, tutorials, libraries, etc. Just that it's another issue, aside from the individual words themselves, which is often overlooked by monolingual people.
What do you mean by that?
I'm no linguist, but I have some Japanese language ability, and Japanese seems to be pretty different, grammatically, from English, so I'll draw on it for examples. I also had a quick look at some Japanese-centric programming languages created by native speakers and found that they were even more different than I'd imagined.
Here's a first example, from an actual language, "Nadeshiko". In pseudo-code, many of us would be used a statement like the following:
Here's a similar statement in Nadeshiko, taken from an official tutorial:
A naive translation of the individual words (taking some liberties with English) might be:
I know, I know, "displayment" isn't a real English word, but I wanted to make it clear that the function call here isn't even dressed up as a verb, but a noun (of a type which is often used in verb phrases... it's all very different from English, which is my point). And with a more English-like word order, it would actually be:
Here's another code sample from the same tutorial:
And another naive translation:
And finally, in a more English-like grammar:
And here's a for...in loop, this time from my own imagination:
Becomes:
Naively:
More English-y:
You may have noticed that in all of these examples, the "Japanese" code has little whitespace. Natural written Japanese language doesn't use spaces, and it makes sense that a coding grammar devised by native speakers wouldn't need any either.
Now, do these differences affect the computer's ability to compile/interpret and run the code? No, not at all. Is the imposition of English-like grammar onto popular programming languages an insurmountable barrier to entry for people who aren't native English speakers? Obviously not, as plenty of people around the world already use these languages. But I think that it's an interesting point, worth considering, in a community where people engage in holy wars over the superiority or inferiority of various programming languages which have more in common than many widely-spoken natural languages.
I'm trying to think of examples of this, and I actually don't know that this is true. Here are the examples I can think of:
.method()syntax is similar to "subject-verb" order, but we also havefunction(self, ...)which is the reverse of that.for foo in baris used in a few languages (or sometimesforeach). But many languages use a totally non-English construct, such asfor i = 0; i < limit; i++orfor (auto foo : bar).What else is there?
Drawing on Japanese, which is the only non-English language I have significant experience with,
object.method(parameter)would feel more natural asobject.(parameter)method, possibly even replacing the period separator with a Japanese grammatical construct (with no equivalent in English) that really suits this use case. Even the alternativefunction(self, parameter, ...)would mesh better with natural Japanese grammar as(self、parameter、〜)function. The majority of human languages have sentences which run Subject-Verb-Object, but a handful which includes Japanese run in the order Subject-Object-Verb.I gave an example of an alternative
for...inloop in another comment here, so I won't rehash it here. But following the general flow of Japanese grammar, thatforat the beginning of the statement would feel much more natural as aで(or "with") at the end of the statement, since particles (somewhat similar to prepositions in English) go after the noun that they indicate, rather than before. And since semicolons don't exist in Japanese either, even they might be replaced with a particle like "と".There aren't any big problems here, but a plethora of little things that can slowly add up.
Object wa parameter o method desu