391–400 of 657 posts
And the example showcases implementation of fibonacci sequence and calling it with 10 as parameter.
A nice, straightforward syntax indeed!
Although I don’t speak Arabic, I find it a fascinating and beautiful language.
Earlier quoted context omitted.
You don't need to know English to write code. I wrote my first QBasic and Visual Basic programs (one of them was "photo editor") when only foreign language I knew was German (my native is Russian).
I'm really curious now. If you don't mind me asking, how did you learn the meanings of the keywords when they were in a language you didn't understand? Did you have to learn to translate "for", "while", etc into Russian equivalents?
Earlier quoted context omitted.
> To be frank, "/s" would have totally ruined it for everyone else. Yes and no. Here on HN I see it everyday: good on-topic jokes get downvoted. I suspect this happens because when people are in "HN mode" there comes a sort of earnestness into their state that makes it hard to detect other tonalities. P.S. I needed the FORTRAN bit until it dawned on me…
We need a committee to form standards for sarcasm indicator use in various contexts.
This is at best useless, and at worst harmful. If we start using languages other than English for code, then we'll end up balkanizing the software world. People in humanities departments can talk about things like "Chinese Poetry" and "Continental Philosophy," but in STEM, we should be above that nonsense. I should be able to read code written anywhere in the world and understand what it does. This is the same reason…
Earlier quoted context omitted.
All that said I think there are benefits to confining languages principally to Latin script or making some kind of direct transliteration utility to Latin script since it's the language for ~70% of the worlds population [0]. It's very hard to learn to read and even more importantly hard to type in a different script. [0] https://www.worldatlas.com/articles/the-world-s-most-popular...
It isn't really that hard to learn to read a different script, unless it's logographic. A solid week of study at the outside and then it is just a matter of practice to get faster.
Earlier quoted context omitted.
> Now that I think about it, languages that aren't subject-verb-object probably find OOP insane. I'm not sure if that's true in this generality. After all, "agent.doSomeThingWith(object)" is not a declarative sentence, it's a command . So you'd have to look for languages where imperatives don't have subject-verb-object (as an acceptable) order. I'm sure there exist some, but at least I would expect them to start with…
The agent still needs to hear the complete command to carry it out, so there's no strong pressure to prefer a particular word order. In German, the difference between the imperative "Machen Sie das!" [Do that, you (polite form of address).] and the declarative "Sie machen das." [You (polite form of address) are doing that.] is that the imperative does not put the agent first.
The du/Sie in such sentences is something that's specific to German compared to the other languages I know, which don't need (or even allow) the pronoun: "do this", "faites ça", "gjør det" are all complete sentences. In fact even in German it's specific to Sie, for while you can say "mach Du das", "mach das" is fine as well. (If you speak a different dialect from mine, you might insist on "mache" instead of "mach", but around here that ship has sailed.)
Earlier quoted context omitted.
Sure, if you want to start an international project, then English is a pretty good language to use. However, I have heard people say that all software everywhere should be written in English, including things like personal projects and internal tools for companies in non-anglophone countries. I think that's kind of ridiculous.
Something about non-English comments in source code is really off-putting. That, and if you generally do want people to understand, then you should use English. If that does not matter to you, or someone else, then do not.