For historical reasons, languages and activities tend to be associated. Is the need for programmers to know relevant English technical terms any different from opera singers needing to know relevant Italian technical terms or fencers needing to know relevant French technical terms?
Regards – Bhaskar On Tuesday, May 7, 2019 at 12:33:46 PM UTC-4, skinne...@gmail.com wrote: > > When I first used IBM's UniComal the manual was Danish but the keywords > were English. Sometimes the function names in the examples were Danish. I > un derstand your problem. > > However, I do think that language is irrellevent. The keywords are tokens > that can be replaced programmatically with SED or AWK. You can display all > programs in your native language and write code in your native language, > when you save your code, it then translates that language source to English > language source and then when to edit the English language source you > translate it back to your native language source. > > I once wrote a process in Comal that would read a legal contract defining > a database program, it would parse the file, convert it to C++ code, that > would then compile into a working program. If the program did not perform > as needed, I sometimes had to write new C++ code but more often the sale > person would have to do a change order on the contract for the software. > > I do think that all programmers are multi-lingual, they have their native > language and one or more computer languages. Sometimes it is easier to > learn a new language than to build the tools needed to remain in ones > current comfort zone. > > My final comment is a bit off topic, I do not consider English to be a > language, it has over 120,000 words. If you have a vocabulary of 500 words > of Latin you can read most any ancient history. ESL speakers typically have > a subset of only 3k words. Most native English speakers use only 10k-20k > words depending on their training and locale. Native English speakers can > sometimes be incomprehensible to ESL or other English dialects. Vocabulary > can be vastly different depending upon class, heritage, region, training. > > On Monday, April 29, 2019 at 12:36:37 AM UTC-5, Chris Burkert wrote: >> >> I recently read an article (German) about the dominance of English in >> programming languages [1]. It is about the fact that keywords in a language >> typically are English words. Thus it would be hard for non English speakers >> to learn programming - argue the authors. >> >> I wonder if there is really demand for that but of course it is weird to >> ask that on an English list. >> >> I also wonder if it would be possible on a tooling level to support >> keywords in other languages e.g. via build tags: // +language german >> >> Besides keywords we have a lot of names for functions, methods, structs, >> interfaces and so on. So there is definitely more to it. >> >> While such a feature may be beneficial for new programmers, to me it >> comes with many downsides like: readability, ambiguous naming / clashes, >> global teams ... >> >> I also believe the authors totally miss the point that learning Go is >> about to learn a language as it is because it is the language of the >> compiler. >> >> However I find the topic interesting and want to hear about your opinions. >> >> thanks - Chris >> >> 1: >> >> https://www.derstandard.de/story/2000101285309/programmieren-ist-fuer-jeden-aber-nur-wenn-man-englisch-spricht >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/f9e6b57b-7c71-4664-9456-70ba55be804c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
