Live data from Hacker News

Non-English-based programming languages

en.wikipedia.org

161–170 of 228 posts

Re: Non-English-based programming languages

#161

Earlier quoted context omitted.

Lower-case words have a wider variety of shape, as so many letters have markings extending above and below the horizontal lines that bound the letter o. UPPER-CASE WORDS ARE BASICALLY ALL RECTANGLES OF VARYING WIDTH AND FIXED HEIGHT. BUT THEY USE MUCH LESS WHITESPACE, WHICH IS WHAT LOWER-CASE WORDS USE TO CARVE OUT SHAPE. I believe the result is that lower-case words are easier to read at sufficiently close distance…

Word shape is not a well-supported theory of reading. Very skilled and practiced readers are still going letter by letter. "The result" is that if you pull people off the street and ask them to read capitalized or lower-case text, they're slower at reading the capitalized text. People like pasabagi want to leap to the conclusion that that means reading capitalized text is harder. That conclusion is unjustified; the r…

Your ideas seem a bit counter-intuitive, so I'll assume they're coming from some literature, and I guess I can't really comment on literature I haven't read. All the stuff I've found (partially what motivated my interest in the first place) were studies showing the opposite, written in the days when ALLCAPS was the normal form of written communication.

Re: Non-English-based programming languages

#162

Earlier quoted context omitted.

> Programming uses the same words as regular English, but it is a completely different linguistic register, so there is never any conflict. Moreover, when you cross over those jargon terms into their regular meaning, hilarity ensues. For example, you can easily prove that oaks are infinitely tall in winter. Start by observing that in winter, oaks don't have leaves. Then consider the graph-theory definition of "tree"…

Alternatively, oaks do not have any nodes at all in winter

It depends, do they have any branches?

Re: Non-English-based programming languages

#163

Earlier quoted context omitted.

> Programming uses the same words as regular English, but it is a completely different linguistic register, so there is never any conflict. Moreover, when you cross over those jargon terms into their regular meaning, hilarity ensues. For example, you can easily prove that oaks are infinitely tall in winter. Start by observing that in winter, oaks don't have leaves. Then consider the graph-theory definition of "tree"…

Alternatively, oaks do not have any nodes at all in winter

An oak without nodes? Pretty sure that's just a seed.

Re: Non-English-based programming languages

#164
post #143
post #24

Seeing a programming language in your native language after working with English ones, you discover that it looks and sounds pretty ridiculous. My belief is that the native language is ingrained on a low level in the brain, so it's decoded ‘in the hardware’ and directly invokes meanings and associations, whereas a second language goes through at least some level of conscious processing. The very same way, I'm physica…

French here, that's my experience as well. I want to emphasize that the huge majority of the non-english native programmers I know are pretty opposed to translating programming languages. However, my experience teaching Japaneses has been that what is crucial if you want to make a programming language accessible to different nationalities is to translate error messages correctly. Learning IF, FOR, RETURN is not hard.…

Cannot agree on error messages, had opposite experience with them. I always require all team members to install English versions of runtimes because it is easy to search non-trivial errors on the internet. Many translations are automatic or done by not very technical people and they sound weird in local language, e.g. many terms in Russian, even such simple as "heap allocation", are really weird. An English error that you see for the first time is usually solved via quick search with the first result usually linking to StackOverflow with the correct fix, but with the local language it's often difficult to understand where to start. (But basic English knowledge is assumed)

Re: Non-English-based programming languages

#165

Earlier quoted context omitted.

"When camping, I enjoy pegging the guys" can also have a wildly different (sexual) meaning.

Our friend @inopinatus was certainly making that joke.

Not sure what you mean. In this example, I’m just pitching a tent.

Re: Non-English-based programming languages

#166
I vaguely remember reading about a fuckup where the translation department of a company (I believe it was Microsoft) accidentally translated the entire programming language (I believe it was PostScript) into German. Of course you were no longer able to print using the german version of PostScript.

Does anyone else know what I'm referring to? It was probably in the late 90s.

Re: Non-English-based programming languages

#167
post #143
post #24

Seeing a programming language in your native language after working with English ones, you discover that it looks and sounds pretty ridiculous. My belief is that the native language is ingrained on a low level in the brain, so it's decoded ‘in the hardware’ and directly invokes meanings and associations, whereas a second language goes through at least some level of conscious processing. The very same way, I'm physica…

French here, that's my experience as well. I want to emphasize that the huge majority of the non-english native programmers I know are pretty opposed to translating programming languages. However, my experience teaching Japaneses has been that what is crucial if you want to make a programming language accessible to different nationalities is to translate error messages correctly. Learning IF, FOR, RETURN is not hard.…

No way. I hate localized error messages. At least in modern times as software vendors stopped putting error numbers into the message.

It's very hard to find solutions online when you only get a localized error message.

Re: Non-English-based programming languages

#168
post #143

Earlier quoted context omitted.

French here, that's my experience as well. I want to emphasize that the huge majority of the non-english native programmers I know are pretty opposed to translating programming languages. However, my experience teaching Japaneses has been that what is crucial if you want to make a programming language accessible to different nationalities is to translate error messages correctly. Learning IF, FOR, RETURN is not hard.…

Cannot agree on error messages, had opposite experience with them. I always require all team members to install English versions of runtimes because it is easy to search non-trivial errors on the internet. Many translations are automatic or done by not very technical people and they sound weird in local language, e.g. many terms in Russian, even such simple as "heap allocation", are really weird. An English error tha…

I guess this is where error codes come in handy.

Re: Non-English-based programming languages

#169
post #168

Earlier quoted context omitted.

Cannot agree on error messages, had opposite experience with them. I always require all team members to install English versions of runtimes because it is easy to search non-trivial errors on the internet. Many translations are automatic or done by not very technical people and they sound weird in local language, e.g. many terms in Russian, even such simple as "heap allocation", are really weird. An English error tha…

I guess this is where error codes come in handy.

Not actually unless it's a native OS exception with a well-defined hex code. I was talking in .NET context, and when you get e.g. some SocketException related to setting up UDP multicast parameters only textual description helps for highly relevant search with double quotes. Often there are just no results at all in local language for highly specific complex conditions.

Re: Non-English-based programming languages

#170
(non-native speaker, learned programming before English) I think this is a bad idea for a few reasons:

- More languages = more barriers. Gosh we have enough problems with silos within the software dev community as well as languages in real life being one of the main hindrance to mobility. - Learning how to program is a great opportunity to refresh your mind and adopt a new way of thinking, why carrying along the burden of your flawed human language?

Post reply on HN