this post was submitted on 19 Nov 2023
52 points (83.3% liked)

Programming

17507 readers
9 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

Github: https://github.com/nasser/---

Hello world:

‫(قول "مرحبا يا عالم!")
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -4 points 1 year ago (4 children)

Sweet, we need more non-English programming languages. I'm surprised that existing programming languages haven't been translated yet.

[–] BatmanAoD 13 points 1 year ago (1 children)

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:

  • 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
[–] Redkey 0 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] robinm 5 points 1 year ago (1 children)
[–] Redkey 2 points 1 year ago* (last edited 1 year ago)

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.

[–] BatmanAoD 2 points 1 year ago (1 children)

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?

[–] Redkey 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 1 points 1 year ago

Object wa parameter o method desu

[–] Cyno 6 points 1 year ago (1 children)

I'm not disagreeing outright but... Why do we need more non English programming languages? Is there a specific practical reason?

The only language translation I'd maybe consider to accept in programming is Esperanto. Anything else just sounds like a terrible idea.

[–] [email protected] 2 points 1 year ago (1 children)
[–] Cyno 3 points 1 year ago (1 children)

It's a neutral, easily accessible language. Having it in programming could incentivize more people to learn it as well.

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago) (2 children)

English has become the defacto lingua franca. I’d argue that Esperanto is less accessible than English, because barely anyone knowns it.

[–] Cyno 8 points 1 year ago (1 children)

I agree completely. The discussion was what we replace English with however.

I'm not in favor of replacing English, I'm just saying if we want an alterantive I don't want it to be a nation-specific language again, so to speak.

[–] [email protected] 1 points 1 year ago (1 children)

The problem with Esperanto is that it's still very euro centric. I might nonetheless be willing to learn it, just because I get a kick out of watching native English speakers trying to speak a foreign language

[–] [email protected] 1 points 1 year ago

Esperanto is eurocentric, because it's international. Because romance languages where made by colonialism of the roman empire. The argument goes of "equality". Thinking the other way around would be that asiatic languages colonized the world, then Esperanto would be based on asiatic languages.

Esperanto is a pragmatic language, not a "totally neutral" language. If you design a language to be "totally neutral" then parts would be distributed differently. How to chose which vocabulary of languages should be used often?

So using romance languages is a pragmatic solution to this. Through usage words can be added or fall out of use, all that is allowed in Esperanto and which can make the language out of colonialism in the future more egalitarian.

But it's ignorant to ignore Esperanto at all and morally vilifying it as "eurocentric therefore bad".

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago)

Every book is not "accessible", when it's not even opened and willfully ignored of existing.

There is:

  • https://lernu.net
  • [https://esperanto12.net/en](Esperanto in 12 days)
  • [https://www.amazon.com/Complete-Esperanto-Learn-write-understand/dp/1473669189](Complete Esperanto)
  • [https://en.duolingo.com/course/eo/en/Learn-Esperanto](Duolingo Esperanto)

There are languages to which it's less accessible, but from the bigger ones, it's quiet accessible.

But if people don't open their eyes they don't see the forest in which they are standing.

[–] SpeakinTelnet 5 points 1 year ago

The main issue is programming in a specific language limit who can contribute to those who speaks that language. In that sense English makes sense as it is already a widely used language in a work context. It would probably limit those who are willing to use the software as it makes auditing harder.

[–] [email protected] 2 points 1 year ago

well there's Logo which is translated to many languages - e.g. Hungarian in Comenius Logo, so great chance you can instruct at max 4000 turtles on your screen.

also, Excel functions are too localized and using them feels somewhat surreal 😆