Citrine: Localized Programming Language
citrine-lang.org
Citrine: Localized Programming Language
1–10 of 72 posts
Re: Citrine: Localized Programming Language
#2Re: Citrine: Localized Programming Language
#3I have wondered if non-English-speaking universities have to teach their CS courses in 25-50% English, just due to the syntax of the programming languages generally being in English
Re: Citrine: Localized Programming Language
#4Re: Citrine: Localized Programming Language
#5This is cool! Has anyone here taken a computer science course in another language? I have wondered if non-English-speaking universities have to teach their CS courses in 25-50% English, just due to the syntax of the programming languages generally being in English
Re: Citrine: Localized Programming Language
#6One day that audience might extend to women.
Re: Citrine: Localized Programming Language
#7This is cool! Has anyone here taken a computer science course in another language? I have wondered if non-English-speaking universities have to teach their CS courses in 25-50% English, just due to the syntax of the programming languages generally being in English
Re: Citrine: Localized Programming Language
#8I've said too much about this subject in the past [1], but my litmus test for "localized" programming languages is a Korean support (both because I speak it natively and because it is very much different from most Indo-European languages). It spectacularly fails. At the very least it is evident that Citrine only ever cares about languages with prepositions (e.g. `x on: 'greet:' do: { ... }`). [1] https://news.ycombin…
That is to say: language keywords, function and variable names, comments, documentation, and perhaps even multi-token structures might all require associated translation strings.
And as with translating an application (or any text, really), the source material might be written in one native language, and only later be translated into others based on demand and interest.
Software projects have the interesting property that partial translations might make sense under some circumstances. A commonly-used API function could be translated first, for example.
It'd be impressive to work on a project where multiple developers are each individually contributing to literally the same codebase, but each reading and writing it in their own native language(s).
(clearly a situation like that would require a lot of input from translators too - ideally with context for the software language and the project itself)
Re: Citrine: Localized Programming Language
#9> designed to allow every man to write code in his mother tongue. Hopefully, by doing so, Citrine will make coding accessible to a wider audience. One day that audience might extend to women.