this post was submitted on 20 Nov 2022
6 points (63.6% liked)

General Programming Discussion

7814 readers
1 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 5 years ago
MODERATORS
Cloak@lemmy.ml
Restioson@lemmy.ml
6
International auxiliary languages should be utilized in software development (to improve international collaboration). (lemmy.ml)
submitted 2 years ago* (last edited 2 years ago) by Amicchan@lemmy.ml to c/programming@lemmy.ml
40 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] Amicchan@lemmy.ml 3 points 2 years ago* (last edited 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())