Given that international auxiliary languages allow for more efficient cooperation; I think more people should consider using an easily learnable IAL, like Esperanto.
IALs would reduce the English dominance that gate-keeps software development to English persons; and hence allow more potential software developers to better develop software. The English language is mostly dominant in software development because of linguistic imperialism.
Both. I don’t see what’s wrong with integrating IAL support with programming languages; though it shouldn’t be forced upon others.
it takes like 2 minutes max to learn all the english words used in programming languages, additionally, parsing for smth like c++ is already an absolute nightmare, needlessly complicating it is … needless
When I was looking at Mastodon Desktop clients a while back I came across Mikutter, which is only in Japanese. In their FAQ was a little gem which I feel may be relevant, the question “I am English speaker. Can I use Mikutter in English?” The response was in Japanese, here it is translated:
How a programming language is written is a legitimate concern.
Yeah, that right there is why I’m trying to fight against the English hegemony (through using Esperanto more in my programming projects). No one should be left out of contributing to a project just because the development industry systemically enforces foreign speakers to learn a national language of some far off country.
If you’re a native English speaker. If you’re not, expect to take longer to understand what an English term means (and also to deal with the English language).
Even if they understand the English term, someone might not be readily able to type an English character.
Parsing wouldn’t be any harder with different languages. There are programming languages that have been designed in different languages.
It wouldn’t be too difficult to add support for interpreting non-ASCII tokens or syntax (literally just add the ability to recognize UTF-8); in contrast to the bigger task of creating the parsing mechanism.
There’s always using the good old syntax of LISPs if the syntax gets complicated.
EDIT: Actually, Esperanto is compatible with ASCII under the H/X spelling system; so Esperanto in particular doesnt need UTF-8 support. The only change needed is to change the tokens themselves. (main() to chefo())