3 ms·
As engineers I think we can all see the benefits of having a standard language to back keywords. I mean, culturally it's nice to have many languages throughout
by jobigoud 10y ago
As engineers I think we can all see the benefits of having a standard language to back keywords.
I mean, culturally it's nice to have many languages throughout the world but imagine how easier everything would be if everybody on the planet spoke the same language. Now imagine if you had to relearn the name of "true", "false", "if", "for", etc. each time you change language… Bonkers.
Anectdote: As a non native speaker myself, I learned to use the while loop before I knew what the word "while" meant. The subset of English words used in programming can be learned pretty quickly.
So, yes, it is not worth it IMHO. For better or worse, English is the way to go.
- holaboyperu 10y agoYes, I agree with you with most of what you said, however, there are dozens of programming languages in English that don't get enough attention, why can't a non-English language be popular in its part of the world?
- Tomte 10y agoAh, the times when Microsoft translated VBA keywords into German... But while they gave that up, we still have localized Excel function names. I don't know how robust exchanging Excel files really is, it makes me nervous, at least. But given that many companies are global now and Excel is an important backbone to any company, there cannot be more than rare and minor problems with it, I guess.
- jobigoud 10y agoAnd also the netsh urlacl command line where you have to put the standard user group name "everybody" in the computer's locale. https://stackoverflow.com/questions/18855607/create-sddl-failed-error-1332 https://stackoverflow.com/questions/18855607/create-sddl-fai...