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.

  • vitaminka@lemmy.ml
    1·
    2 years ago

    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

    • Amicese@lemmy.mlOP
      2·
      2 years ago

      it takes like 2 minutes max to learn all the english words used in programming languages,

      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.

      additionally, parsing for smth like c++ is already an absolute nightmare, needlessly complicating it is … needless

      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())

    • Dochyo@lemmy.ml
      1·
      2 years ago

      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:

      After the defeat in the war, the Japanese were forced by GHQ to adopt Shift-JIS and JAP106, and as a result, they fell far behind in the development of information technology. When I was in elementary school, when I started programming, I was frustrated because I was lined up with English that I had never learned. Also, you have released many low-quality services that do not support anything other than ASCII, which even Japanese elementary school students would not create. This mikutter is a precious opportunity for you to relive how we have been oppressed for generations.

      How a programming language is written is a legitimate concern.

      • Amicese@lemmy.mlOP
        1·
        2 years ago

        When I was in elementary school, when I started programming, I was frustrated because I was lined up with English that I had never learned. Also, you have released many low-quality services that do not support anything other than ASCII, which even Japanese elementary school students would not create. This mikutter is a precious opportunity for you to relive how we have been oppressed for generations.

        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.