Timeline for answer to Iterating over split string by NickJ
Current License: CC BY-SA 3.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2014 at 10:45 | comment | added | zmo | All I'm praising for is consistency. Computers, languages, libraries and tools are all written in English for historical reasons first, but since then, for homogeneity. What if one day, you get to work on a code I have written with french variables, that another Hungarian guy took over and added hungarian variable names, which then has been patched by a korean guy who used korean names for variables? Won't you just loose your head? The level of english needed to write into a given language is somehow the same as the one needed for 90% of variables. For the 10% left there's google translate | |
| May 21, 2014 at 10:41 | comment | added | NickJ | I've always felt that non-native English speakers are discriminated against when it comes to software development because, as you say, all language keywords are in English. I was assuming that using your own language for variable names might help, but as you are a non-native English speaker, you would be a better judge than I. | |
| May 21, 2014 at 10:20 | comment | added | zmo | actually it's always a bad idea to use variable names in french (or any other language than english). Because the keywords of the language and the name of the methods are in english and mixing languages will ultimately create confusion. N.B.: I'm not a native english speaker, and I've been fighting against that for many years. | |
| May 21, 2014 at 10:16 | history | answered | NickJ | CC BY-SA 3.0 |