Japanese explained to programmers
lajili.com
lajili.com
— So You Want To Learn Japanese http://www.stmoroky.com/links/sywtlj.htm
The one-to-many relationship between a given kanji and its many pronunciations makes it maddeningly difficult, even for native speakers. 生, for example, has at least nine pronunciations. The only way a programmer might “solve” Japanese would be with copious use of lookup tables or prefix trees.
The thing is though, humans don't actually read alphabetic orthographies by the individual letters, but rather by the overall shape of the word. THAT'S WHY ALL CAPS TEXT TAKES YOU SO MUCH LONGER TO READ (letters lose their unique shapes). And taht's why yuo are gnaelrely stlil albe to udnersnatd tihs txet dispete me scrambling the central letters.
Alphabetic orthographies may seem more extendible, but ultimately teaching kids to read is still a matter of teaching them to memorize a vocabulary. There's a benefit to alphabetic orthographies that sometimes shines when you encounter new words, but the level of information you can encode with a syllabary is much higher and generally not actually any harder for kids to learn than alphabets
[citation needed]
It’s not clear how you can encode any more information with hiragana/katakana - the Japanese syllabaries - than you can with an alphabet. Indeed, it’s fairly clear the reverse is true - you can only really encode sounds for which the syllabary has symbols; conversely, as English demonstrates, you can encode a vast array of sounds while only having 26 distinct letters.
Orthographic English is probably the best example to show the inefficiencies alphabets sometimes bring. The English language has ~24 constants which are often well-represented, but then you have things like "ng" or "sh" which is actually a single phoneme that we lack a symbol for. On the flip side, English has an unusually large number of vowel phonemes, around 13 monophthongs and 7 dipthongs. Yet we have only 5 symbols for vowels and often use them in very ambiguous and end up having strange combinations of them leading to ghoti:
https://en.wikipedia.org/wiki/Ghoti
The point is you only have 26 letters, but now you end up having to memorize a vast array of combinations and how they work in different contexts. You're really not saving yourself any more memory space than if you'd learned a syllabary
What you lose with syllabary is to be able to encode some patterns - like Czech "strč prst skrz krk" - pretty much no way to encode it in Japanese I think, unless you resort to a lot of cheating like inserting "u" everywhere and then declaring "u is silent" (which is pretty normal for Japanese in general but in this case kinda looks like cheating). But tbh English encoding wouldn't adequately describe how it's pronounced either.
This is pretty cool
For the party trick to work the words of the language in question must have relatively short words, and suitably small but syntactically heterogenous paradigms for any given lexeme, with changes expressed mainly by the end of the word. (Paradigm: for example conjugations are paradigms of verbs, declension are paradigms of nouns; lexeme: "fundamental base word").
In some languages individual letters in the middle of the word morph as the meaning of the word changes (different tenses of verbs, different number or gender of people/objects, whether an action is ongoing/finished/planned, whether a statement is a question or a command).
The "many pronunciations for one kanji" thing isn't a problem in practice, because 1) most kanji have _1_ on'yomi (Chinese) and _1_ kun'yomi (native) pronunciation, with it being obvious which one to choose from context, especially because when it's kun'yomi, the kanji are suffixed with hiragana to denote its correct pronunciation. There are however problematic kanji, such as the one you note, because there are several things it could mean, but this isn't really any different from _all_ languages.
Given any sentence, there are multiple possible meanings, and we have to disambiguate depending on context. This is true even for sentences like "The man is here", which man?
The part about complexity is less "ambiguity", and more "how much headspace do you need for the language". I'm not sure if Japanese is more complex than English in that regard, but I do want to note that 1) pronunciation is very straightforward 2) it's *very* hard to make spelling mistakes 3) there are very few irregular words.
Especially point 2 is quite important IMO. If you look at rates of dyslexia, you'll see that they're much less in countries that use Chinese characters. Interestingly, many Japanese people whom I know, who have no issue spelling in Japanese, show the very common signs of dyslexia when spelling in English.
I think it's related to there being fewer ways to "fuck up". In English, it's easy to mix up the letters, transpose them, etc.. With Chinese characters/kanjix, _you can't transpose strokes_ digitally. There are people who make mistakes when writing by hand, but even that is much less when writing kana, the reason being that while in English, "relatiounally" and "relationally" might be similarly, transposing whole kana changes the pronunciation such that it's entirely distinct. Transposing strokes within a kana is of course still possible.
Phonetic syllabaries like hiragana may eliminate spelling mistakes, insofar as such a thing could be conceived of in Japanese, but the same is largely true of Spanish, which manages to achieve orthographic consistency while using the same letters as we do.
They don't transpose the strokes, they just forget how to write the character entirely, even if they can read it perfectly: https://en.wikipedia.org/wiki/Character_amnesia
I live in Japan and I have seen it happen many times, suddenly the person needs to stop and check the character in their phone or a dictionary. I have never seen it happens with an alphabet-based language. Sure, you might not be 100% sure about the spelling, but you can always approximate it and write something.
Every single Japanese person who I know has told me how much a pain in the ass their language is to read and write, and how they wish it was simpler, but shoganai.
I got it once for a couple of days when I was about 7 years old. Learned how to write an uppercase N, and became unable to write it lowercase (n) for a few days. (it's a super weird feeling, trying to write something and producing a different shape)
What the heck...? It's most definitely a problem in practice! That problem becomes pretty obvious once you get a vocabulary of around 10k ~ 15k words and you read both fiction and non-fiction books. What you find is that every time you encounter an unfamiliar word you only really have a best guess at how to read it and you actually can't be 100% sure. This has repeatedly been my experience. I spent some time thinking about if I could shortcut this process by instead simply learning all the "exceptions to the rule" but what I discovered is that the volume of them is too large for that to be a tractable approach.
The feeling I am getting from this discussion is there are quite a few people who have dabbled in the spoken language without having to grapple with its intractable writing system but consider themselves experts regardless. Anyone who looks at English and Japanese and finds them to be of equivalent complexity probably isn’t qualified to comment on either.
The existence of furigana alone is a huge admission that Japanese a somewhat unreadable language that has somehow or other been made to work through bolting it on. So, you can imagine that if an orthographic system comes with permanent training wheels for native speakers, then non-native speakers are going to have a pretty brutal time with it.
Logograms allow you to understand (some) meaning without understanding pronunciation.
Syllabaries and alphabets allow you to understand pronunciation (to varying degrees of success depending on spelling consistency) without necessarily understanding meaning.
It's all tradeoffs.
These days I read Chinese much better than Japanese, and it's definitely fun that I can look at a page full of Japanese and understand the meaning of many words just from knowing the (largely parallel) meaning of the kanji / Hanzi from Chinese.
Conversely, I can read (the sounds of) Hangul, but I rightly know about 20 Korean words, so it's all just sounds to me.
But I can read the name off of a Korean hotel sign and communicate it to a Korean taxi driver. I can't do the same in Japan if I don't know the pronunciation, even if I know exactly what the sign means. If it affects your ability to use the language effectively to achieve what you want then I think it matters.
For instance, on the 1 onyomi with 1 kunyomi average, there’s no specific logic making it that way (I actually doubt it’s only one of each in average), and there’s no limit on how many readings a kanji can get, people can randomly add new readings and popularize them.
It’s not a problem in practice because not knowing most words’ reading has little impact in day to day life, and mixing up kanjis is pretty common and people won’t make a fuss about it.
All in all I think Japanese has a very steady learning curve where other languages will have sudden walls to climb, but it’s not more or less complex, difficulty is just more evenly distributed.
Precisely! It is insane. Song lyrics are a case in point. It is the height of erudition to contrive a novel way to write some verb or other.
Furigana are essential for karaoke.
This is intensely interesting -- do I understand this correctly, that what happens is a songwriter uses a verb (or I guess any word) and writes it down as a different set of kanji(+kana) than how it's usually written, and the new form is confusing at first to a reader of the lyrics, and the new form evokes some different emotion or context because of the choice of kanji?
Can you think of an example? I want to see for myself.
Wordplay is delicious and I've never heard of this kind of it. . o O ( this had better not awaken anything in me. )
There are always several ways to write a word in Japanese. As far as I know, any word can be written in hiragana. Additionally, there are the kanji writing and then katakana. While katakana is primarily used for words that were appropriated from other languages, it has several other common uses. For example, if a robot, alien, child, or non-Japanese is speaking, the words may be written in katakana to indicate the non-fluency of the speaker. Also, many animal names are often written in katakana.
Additionally, there are quite a few pseudo-English words that are written in katakana because they originally arose from English words. Some of my favorites (written in romaji for those who don't read katakana):
- "baabeekaa" : pronounced similar to "baby car", this word means a stroller
- "akogi" : short for acoustic guitar
- "brappi", "jimihen", etc: Brad Pitt, Jimi Hendrix, etc.
- "handoru": pronounced similar to "handle". This is what a steering wheel is called in Japanese, so..
- "handorukeepaa": or handle keeper, refers to a designated driver.
Another interesting thing that occurs in Japanese is referred to as ateji. This is where kanji are used only for the sound they give. In other words, any word can be written by just using a kanji with that sound for each syllable. The meanings of the kanji chosen (there are many with each particular sound) can give additional flavor/wordplay/signifigance to the usage.
Finally, one of the most interesting things I saw in Japanese was a baby soap, called "Arau baby". The first word "arau" is the Japanese infinitive for "to wash" written in romaji, or roman script. Since this is the product name and it is written in roman script, the product label also includes a katakana translation (アラウベビー). So instead of using the kanji for arau, it was treated as a foreign word and then appropriated back into Japanese using katakana. Or something.
There is just absolutely all sorts of fuckery in Japanese on a count of people playing with the language. It's a fun language to play around with.
(I will try to dig out a relevant song lyric.)
Traditional examples would be 本気 (honki) -> マジ (maji), 頭文字(kasiramoji) -> イニシアる(initial), 因果(inga) -> カルマ(karma)
I remember a live stream where a comment with "超電磁砲"(choudenjihou) was straight read into "railgun", as at this point the novel/manga/anime just established it as a popular reading.
One good example is from GReeeeN's 愛唄(Aiuta/ Love Song). It's a song about a guy apologising for all the times he's fought with and been a nuisance to his partner, and reaffirming his love for them.
「君の選んだ人生「みち」は僕「ここ」よかったのか?」
Taken as you'd hear it from listening to the song, it means "Are you happy with the road you have chosen?", but reading the lyrics uses different kanji to give it a slightly broader meaning.
人生 is read as jinsei, meaning life, but the furigana is 道(みち)which is a road or a path, note that this can be a literal road or a more figurative pathway through life.
僕(boku) is a male pronoun for "me/myself" but ここ means "this" as in "this road, not that one"
It's not that deep, but it extends the meaning of the lyric to be something like "are you happy to spend the rest of your life with me?" I thought it was kinda clever. There's probably better examples, but this pops into my head often as it's still quite a popular song.
let's take something very basic, the kanji 人 has two on'yomi pronunciations, jin and nin and there's no way to tell which one to use without knowing ALL of the words it will be used in
日本人 - nihonjin, so far so good 三人 - sannin, okay, I guess there's two pronunciations 二人 - futari, huh? 一人 - hitori, wat
so please tell me how I am supposed to know 人生 (jinsei) from 人気 (ninki) from 恋人 (koibito) from 大人 (otona)
even ignoring the irregular reading for "adult" there's still no way to tell those three readings apart in a kanji as basic as person
As far as jin and nin goes... (source: 漢語からみえる世界と世間)
jin is more about adjectives/nouns - describing yourself, and part of your identity. 日本人、アメリカ人、原始人、現代人 are all じん. 読書人(どくしょじん) is used to describe people who really love reading. Similarly 暇人(ひまじん).
nin is more of a plain descriptor. 管理人、運搬人、苦労人、被告人 are all にん, as well as 三人.
Why is popularity "plain" and humanity is "identity"?
You just have to memorize ALL of the compounds, there's no other way
Your question about the reading, though, has quite a simple answer. It's pretty obvious how to read all the examples given when you look at them as words, not a single character. Kanji does not exist in a vacuum. 人気 is "ninki" and 大人 is "otona" - no other way around it. Combination of those characters, usually, have one and only reading. To tell the truth, in English, people are unconsciously reading words as a whole, too.
if it's 大人気ない it's probably childish, but if it's not in that context, it's probably very popular
You need to finish reading the whole SENTENCE to be able to pronounce it
大人気なくてもいい means it's okay to be childish
Or we could enumerate the pronunciations of 日: 日々、日曜日 (which is top-tier insane), 日本、春日、本日、明日、明後日、今日 (take your pick which one I mean), 昨日 (ditto), 一日 (ditto), 二日、十四日〜十五日、二十日〜二十一日。。。
One can marvel at its complexity - relish it even - but one cannot deny it.
Also sometimes 受入 is written 受け入れ instead! And 支払い can be 支払. It is really confusing.
Knowing all these nuances is difficult if you are looking to just use simple rules here and there.
Although using an app released in 2022 in Windows Shift_JIS compatibility mode is giving me less than regal feelings. /s
Accounting Japanese is another whole weird world of unusual Japanese, such as 支払手数料 (payment fees) suddenly applying to all kinds of non-fee things as well such as professional services.
One should keep in mind here that IT Japanese uses Japanese in places you won’t expect, and when you expect it even less, it will switch back to English.
That there would be Japanese software houses still using Shift JIS in 2022 does not surprise me in the slightest. Presumably they still deliver you software updates by floppy disk, notification of which comes by fax…?
Kaikeio doesn't support HiDPI / 150 % fractional scaling either, so it looks really weird on my machine.
Recently the maker (Sorimachi) has announced that you can download their newest edition. Too late! They have already sent me the CD.
Anyway, you know it's completely wild when their official help site points you to switch to Shift-JIS compatiblity mode on a fresh install of Windows 11 :) (https://qa.sorimachi.co.jp/hc/ja/articles/360054408631-%EF%B...)
I just resort to editing everything in GnuCash and then importing into Kaikeio using a custom sql -> csv script. I hate the idea of my accounting journal being trapped in proprietary software.
Too bad that Japanese lawmakers have further decided to decrease software freedom by prescribing the use of digital time stamping by next year.
I agree that it’s very strange that professional services fall under 手数料 instead of 報酬, but taxes are weird in every language.
Anecdotal, but considering how often I see Japanese people have small struggles with their own language compared to British or American people, I think it is more complex than English.
If you look at verbs, and ignore the rubbish written in most textbooks about "conjugations" (which for the most part aren't conjugations), you'll find one of the most logical and consistent systems on the planet. There are only two exceptions. How many exceptions are there in English?
EditAdd:
What English does have is a lot of redundancy, which can cover up tons of grammatical mistakes and still deliver the meaning. This makes it an excellent language, in many ways, for international communication. If you try to speak someone else's language, and that person knows just a little bit of English, that person can make a lot of mistakes and the meaning is still clear enough, particularly if you're a little practiced in listening to non-native English. Whereas you may make a small little mistake when trying to speak that person's language, and suddenly the sentence totally changes. Heck, even Italian.. use the wrong verb form and instead of saying what you meant "Ah, I'm stupid" you're saying "Ah, you're stupid". But it's hard to mess up English that way so easily.
I mean, fine, if we are going to contrive a comparison where we are only comparing spoken forms, well…English is still going to come out on top, because - exactly as you explained in your edit - its grammar is simple enough that almost anyone can have a go at it. Stick some words together and you’re probably 80% of the way there. That’s not going to be true of any inflected language, even if - as inflected languages go - Japanese is one of the simplest.
Anyway, if we are going purely on grammar and ignoring written forms, Chinese - having almost no grammar at all [citation needed] - is surely the apex of simplicity.
As for English.. "I is to town goes". Mess it up in every possible way and the meaning is still the same, most of the time.. which is arguably very useful for trying to communicate with someone.
A language without its written form is a language. The written form is an artifact of modern society and literacy.
Similarly to people thinking less of the country they were born/raised, I tend to find that people always think their first language(s) are the less logical ones, maybe that fits in here as well. Some sort of bias it seems.
English is grammatically fairly simple, having dispensed with much of the (redundant) complexity found in its European brethren (gender, case, almost all inflection). I would argue that that makes it fairly easy for beginners to develop a basic command of it. Its main problems are its unpredictable spelling (does any other language come close? French is a bit of a mess, but nowhere near as bad as English) and its love of a phrasal verb (what do get up/on/down/over have to do with each other?).
I frankly gave up with English grammar and just did whatever feels right.
Thank you! It is heartening to hear this from a native speaker. Phrasal verbs are… a pain. “Burning up” pretty much is “burning down”? Oh, the list is long.
She must have had been being watched.
= It must be the case that someone watched her for some duration of time prior to the current moment in the story (which is either a hypothetical story or narrative of the past).
imo that's better than having a whole other system like Katakana to import foreign words.
- "I'm down for that", I am prepared and willing to do that
- "I'm down on that", I don't like that practice
- "I'm down with that", I do like that practiceAs a counter example, I think my first language (Hebrew) is more logical than English. It makes a lot more sense to me to put words that modify or add detail to other words after the word they are modifying instead of before (most notably, it seems strange to put adjectives before the noun they apply to, since logically you should first introduce a subject before adding more details to it). It also feels a lot more logical how in Hebrew you construct words from stems and templates rather than every word being essentially arbitrary.
Though I'll also readily admit that Hebrew has many problems of its own...
"A hot, juicy chicken leg" would sound less exciting if it was said "A chicken leg, hot, juicy" because the listener would first imagine the wrong chicken leg.
(The Japanese equivalent that springs to mind is the word for Sunday, 日曜日, pronounced nichiyōbi. It includes the same Chinese character pronounced two completely different ways within the same word.)
Reading is similar until Kanji comes along and messes things up, but by that stage you could probably get by pretty well, both in the country, and by ingesting materials with simplified Hiragana alongside Kanji (which are common).
I mean, sure, if you exclude the most complicated writing system currently in use in any natural language, Japanese is simple. I hear Chinese is really easy too if you just do everything in pinyin.
Right, sarcasm off. Yes, the grammar is pretty simple. It has a mere three irregular verbs. The inflection can be somewhat unwieldy (温かくなかったら atatakakunakattara, if it were not warm) but it is nowhere near as complex as European languages.
But. You can’t just dismiss kanji. They are the essence of the language and, counterintutively, are what make it easy to read in long form. A stream of hiragana is almost illegible; you need the kanji to be able to pick nouns and verbs out. And outside of very limited contexts, furigana (phonetic transcriptions of kanji) are rare, so you need to a reasonable command of kanji to get by.
Sarcasm aside, I only take issue with this.
The context here is learning Japanese, ie a beginner. A typical way to do that with any language is to use the enormous wealth of resources aimed at either kids or learners. Including in this case many popular manga.
It's a context within which, of course, Furigana is widely available, as it's one of the ways Japanese themselves learn Kanji. And I would guess probably why it even exists, though I'm sure you could correct me on that.
Your view of Japanese seems to be from a very high level, encompassing its totality or close to it. At that level your assertions may be correct and relevant, but that's not where my comments, nor the OP with their post, are aiming.
It's actually many-to-many. I know it sounds crazy, but it's even true for English, just to a much less extent. Sometimes a single Japanese word can be written as different kanjis.
Kanji will have at least two pronunciations (one called a Chinese pronunciation that often sounds little like modern mandarin, like 电 being Dian in Chinese and Den in Japanese).
This list is also changes on a regular basis. The following news article details updates to pronunciation guidance promulgated by the Taiwan Ministry of Education at the end of 2022: https://www.ftvnews.com.tw/news/detail/2022326L08M1
It is my understanding that these new guidelines result in mandated changes to educational curricula as well as standardised testing; they are not wholly advisory. It is also my understanding that these changes can be mildly controversial, because even when the changes are made for the sake of simplification, they lead to discrepancies between the educational standard and common spoken language.
Some characters are moderately logical. A tree, 木, begets a wood, 林, and a forest, 森。日, sun, in triplicate, 晶, is a crystal or glittering. But these are very much the exceptions. By what logic would you create a character for a whale (鯨) as distinct from a salmon (鮭), or for abstract concepts like government (政) or crime (罪)?
or language models
Things are just way harder than they need to be in a lot of instances.
I guess the world is a more connected place now.
I love the language though so I'm personally happy if it sticks around.
I hate grammar and I found that part of the language to be extremely simple.
We have this in English too except remarkably little of it actually comes out. Pluralization and possession being marked with -(e)s and -'s suffixes, and "subject-verb agreement" (one wouldn't say "the birds eats the food" but rather "the birds eat the food") are examples of morphology in action in English.
Several folks think that the capacity for language in general is common to all humans, and that we have some proto-language hidden away deep in our brains, inaccessible, where our conception of the world bubbles up through layers of our brain/consciousness, until thoughts-as-words eventually fall out of our mouths or onto paper, and then the reverse process happens as well.
(Incidentally I think the particle は marks the "topic" of the sentence, not the subject. The subject of the verb is marked with が, and Japanese speakers elide/omit a lot of parts of sentences, so there's tons of sentences where there is no explicit subject but there is a topic. Please correct me here, this is all from faint memory.)
Some languages share more intermediate compiler stages than others (Latin, Italian, French) whereas share a lot fewer (English and Japanese come to mind).
One thing I like about this formulation is that humanity doesn't all need to have the same meat / "hardware" in their brains at the bottom layer (which is kind of unsatisfying and less-plausible, and makes me think of 2001: A Space Odyssey), as long as there is interoperability at the highest layer.
Japanese is extremely regular, which makes the grammar easier to learn though it is completely different to any language with indo-european roots.
For valuable insights into Japanese grammar I recommend 'Making Sense of Japanese' by Jay Ruben (he translated works of Murukami including Norwegian Wood into English).
Also a youtube channel Cure Dolly https://www.youtube.com/@organicjapanesewithcuredol49 Who sadly died a few years ago, but who's insights nonetheless are very helpful (if you can get past the modified voice audio)
It was a coincidence that I had just finished some reviews on wanikani just before reading this. I find it very helpful along with using the Core 2k/6k Anki deck for learning Vocabulary.
But the topic marker does not mark the subject. Any sentence with a topic can remove the topic, and the sentence is still a fully valid grammatical sentence.
For more about this, check out Cure Dolly's excellent videos about the zero-が on Youtube.
Edit: Various typos
(It's also strange because I typoed 牛肉 in my earlier comment, and milk is difficult to eat. Sorry for the confusion.)
Kono(this) nichi(day) wa(is the topic)
今日はご機嫌いかがですか?
if you're a rich girl at a private school you can just say ご機嫌よう
[0] https://en.wiktionary.org/wiki/ローマ字
[1] https://en.wikipedia.org/wiki/Hepburn_romanization#Particles
Chinese is much much easier by an order of magnitude. Particularly if your focusing on speech and grammar vs writing. Not that Japanese writing is any easier.
Hindsight is 20/20. Shoulda took Spanish...
Most people who learn Chinese will never be able to sound Chinese. To Chinese people they will look like some fool who has learning deficits (I know this is not true, but the lack of empathy in mono-cultural nations is quite high). I don't think there's any language in the top 20 most popular that punishes you as hard for incorrect pronunciation. While in English having an accent is quite common and charming, in Chinese bad pronunciation will make things incomprehensible.
For Japanese on the other hand I have multiple friends who after a couple years are indistinguishable from natives. The pronunciation system in Japanese is super easy in my opinion. It's almost a subset of the English language.
Additionally, I think a foreigner who actually puts time into practicing Chinese pronunciation can sound very close to native. Most people learning most languages seem to only aim for good enough pronunciation and then focus on acquiring vocabulary instead.
I don't know what languages you speak, but I speak a good amount of Japanese and will occasionally have a hard time being understood in Japan, probably when the person I'm talking to is not used to talking to foreigners. On the other hand, I've had Chinese people compliment me on my Chinese, and I would not even pass HSK 1. From what I've heard from the Chinese people I've talked to you can get away with a lot of tonal mistakes and still be understood, although you will of course sound like a foreigner.
But yes, the tones are the hard part. The grammar is straight forward and similar to English, and characters are (almost always) pronounced only one way.
I was an immigrant in the US as a teenager and it felt like that in English for me my first few years here. Eventually I got to a point where I can understand stuff without actively paying attention, and it got a lot easier to understand anything with or without context.
As an interesting aside, I speak Cantonese natively, and I barely speak Mandarin. Mandarin to me is like that as well. I have to pay 100% attention to keep up, and as soon as I lose context, all hope is lost in understanding anything in the conversation forward.
(Edit: Added 'basic' - I don't go around trying to explain Japanese grammar in full..)
This means that either there is no good way to track this, or barely anybody gets to a level in Japanese where they would end up in the statistics.
[0] https://en.wikipedia.org/wiki/List_of_languages_by_total_num...
I fail to see how these two things are connected?
Now I live in Europe and joke that you don't see a bunch of Japanese weirdos walking around Brussels dressed up as Tintin.
[1] In the ten years I was there, the number from France was pretty constant, but there was an upward trend in this type of person coming from Scandinavian countries and the US. There is an excellent meme on this matter: https://i.kym-cdn.com/photos/images/original/000/481/981/034...
[0] https://en.wikipedia.org/wiki/Ulysses_31
[1] https://en.wikipedia.org/wiki/Mysterious_Cities_of_Gold
[2] https://en.wikipedia.org/wiki/Dogtanian_and_the_Three_Muskeh...
In general, I get the impression that France and Japan seem to have a deep friendship with each other, on the cultural level.
Also, well, on Japan... Spain, 1500's/1600's, research about "Coria del Río" and be amazed.
Personally I still find a whole lot to love in Japan, which could be an entire post by itself.
This craps me up in Reddit: While we, Western Europeans (France, Spain, Italy, Germany...) have been watching manganime since forever Americans keep lying about DB and manganime availability in the West in early 90's as if the West was just the US.
For instance, the big lie on DBZ knowledge on SNES/MegaDrive games from the West. Fore sure the US didn't know nothing at all. Meanwhile, we were nearly finishing the Buu saga. So we were pretty aware of DB games in arcades, the SNES, the MD and any platform.
I take an issue though with this assertion:
> The order [...] is quite different to english but very similar to functional programming.
The most widely accepted (imo) order of function composition is right to left:
send(makeUrl("http://..."))
just like in English "blue fish": transformation stands to the left to the object that is being transformed (*). Whereas "transformation follows the object" is an OO tradition, as shown in your examples. "Take object, apply transformation (method) yielding another object, apply transformation to that new object, etc."(*) In quintessentially functional Haskell, you can compose functions both ways, but right-to-left is more traditional:
{-
- Find numeric value of the first figure of the decimal representation
- of a number:
- 1. convert it to a string of decimal characters (show)
- 2. take the first character of the string (head)
- 3. convert the character to a string containing one charcter (:[])
- 4. convert the string of one decimal character into an integer (read :: Int)
-}
main = do
let
firstfigure1 :: Int
firstfigure1 = read . (:[]) . head . show $ 413
print firstfigure1
{-
- Reverse the order of composition. Define "right-pointing" versions for
- (.) and ($)
-}
let
(.>) = flip (.) -- it will become infixl 9 by default
($>) = flip ($)
infixr 0 $> -- We need value lower than the above. Use the same as $
firstfigure2 :: Int
firstfigure2 = 413 $> show .> head .> (:[]) .> read :: Int
print firstfigure2> an introduction to how different language can be has different as
It's probably just a simple typo here. But in my head it immediately sounds like a French speaker overcompensating, by adding H's where there aren't any [0], as I have heard this so many times. As a French speaker learning English as a second language, one would learn that H's at word beginnings need to be pronounced in English. And then the brain sneaks them in with English words that didn't have any to begin with, like hangry, or habout. I find the whole topic of overcompensation super fascinating [1]. Another good one is German ESL speakers subconsciously overcompenthating by changing s into th.
I've been to his show, my favorite bit was the one about carrelage: https://www.youtube.com/watch?v=FIqVY1SwXls
I could see the h-insertion leading to comical lost-in-translation situations.
However, in my opinion, an article purporting to inform about Japanese in a programmatic way really should avoid using “hiraganas,” “kanjis” and “katakanas” as pluralization of thise terms.
There's no such thing as "a hiragana".
request.setURL("serverurl").send()
This style of sentence structure was one of the strangest things to get comfortable with. You have to think a bit differently.The function chaining makes sense here and I wonder if the language had influence on Ruby's development.
Anyone interested in the language should definitely check out the Genki series. It's written well enough you could fully teach yourself.
https://genki3.japantimes.co.jp/en/intro/ or amazon.
The primary author of Ruby is Yukihiro Matsumoto, who is Japanese.
What I meant was if Matz "trying to make Ruby natural, not simple" was due in part to the way the language is spoken.
Not only do most Kanji rote-learning resources not take into account aspects such as compound words, but also its just the wrong way to learn Japanese full stop.
No language learning works well if you are continuously translating it back into your native tongue. You need to learn to think in the language you are learning, that is the only way you are going to gain any sort of fluency. Just knowing that X translates to Y is not going to help you, even if you memorise the whole dictionary.
You might get away with translating back into your native tongue with a Western language, but you won't with Japanese.
With Japanese there's no escaping learning the grammar and other aspects. It's just your choice if your want to do it the hard way (textbook theory) or the harder way (immersion via graded readers, conversations with patient natives, or anything else similar).
All the time and effort people put into rote-learning Japanese Kanji should really be expended learning Japanese in a more holistic way.
Otherwise you might as well just buy one of those books with set-phrases such as "where's the toilet".
I'd add that WaniKani does go into compound words, whilst it teaches ~2000 kanji it teaches ~8000 words of vocabulary (which can be either a single kanji, a compound word, etc.). However it does not teach kana only words such as りんご.
As for my own case, I'm self studiying with a grammar book + the minna no nihong + wanikani + a weekly tutor in immersion, playing Animal Crossing every now and then in Japanese and trying to read Komi san, as well as preparing for a 6 week trip, which will be my third trip to Japan. It's hard to imagine doing anything more – my wife already thinks I'm doing too much.
FYI, while this word is most often written in kana it's also often written in kanji.
Source: I run a website with such stats. See "Alt. forms" here: https://jpdb.io/vocabulary/1555480/リンゴ
Where do you get your stats? Honestly, I always see it written as りんご (never katakana, nor kanji), but I don't want to be a Japanese language Internet troll. (Yes, there are many: "Oh, but actually...")
You can either select specific text and ask to "decorate" (kanjis with furigana). Or you can click the extension icon (top right in your browser) and it will decorate the entire page. Mouse over kanjis will show furigana. It was a game changer for me.
> its just the wrong way to learn Japanese full stop
First, let me say that you may be responding to a strawman. There's few-to-zero people who will recommend memorizing kanji to the exclusion of learning grammar and other aspects.
Realistically, people who promote rote-memorization of kanji are also suggesting to learn grammar, attempt to think in the language (not translate in their head), and suggesting immersing/talking/etc as much as possible too.
So, let me ask you, what do you suggest people do instead of rote-memorization of the readings of kanji? How do you suggest someone become able to read a sentence in japanese, guess the pronunciation of an unfamiliar name, if they have not memorized how to pronounce the relevant kanji?
Do japanese school children not learn kanji by rote memorization themselves?
They do indeed, but in a context of everyday immersion, so it’s not rote learning to the exclusion of all else.
Is it just the mention of WaniKani? Personally I don't like WK either, but the author barely mentioned it in passing, and says nothing at all about the stuff you're criticizing.
Rote learning of English spelling is a much more daunting task than rote learning of kanji. To unfairly cherry-pick from the paragraph above, the English word "person" is about 10 strokes; "people" is also 10 strokes. But there is no obvious connection between the two words and the different spellings have to be memorized individually. 人 is two strokes; 人人 is four strokes; 人々 is six? All are easier to memorize, easier to write, and easier to read. Of course, I might have cherry-picked the most extreme comparison. But even that little four letter word "myth" is 9 strokes and must be rote memorized. It is a small word in English. Somebody else can correct my belief that 9 strokes is not short in kanji.
Ok, I'll correct myself. 神話 is a 9? stroke character and a 13? stroke character. So 22 strokes total? It's funny what we convince ourselves to believe when we cherry-pick. "God talk" is a 5 stroke word + an 8 stroke word. "God speek" is 5+10. So even if I go out of my way to justify my belief in Japanese brevity I have to start rethinking. Maybe if I can think of a word like "deity" or something with even more strokes I could eventually avoid having to adopt a new position on which language is easier.
Another observation is the number of times each day a Japanese person whips up their hand as a chalkboard and asks, "This or this?" while air drawing out two different kanji. The fact that the observer can recognize the characters written in air has always seemed instructive to me, though.
Learned Polish recently. It's the same. But people do try the supposedly easy way of learning it "without studying the grammar".
It's perhaps a slower way (unless you go to live for half a year+ in the country and don't use too much the crutch of help available in your languages), but not a harder one (ditto).
Maybe for the very beginning, when you first learn phonetics and alphabet/ideograms, where the "floor" is infamously higher in Japanese for non-~Asians ?
Rote learning and gamified approaches like duolingo have a low barrier to entry; buying a textbook, enrolling in a class or living in the country for a year are much higher and the latter two are prohibitively expensive and time-consuming for casual learners.
The article uses code to illustrate how this might be different thinking in Japanese with a URL request:
> request.setURL("serverurl").send()"
I think there is formality/ceremony here like "I have a request, it is for this URL, and I want to send" vs. the other style in the article: send().request.setURL("serverurl") is more forceful as in "I'm sending you a request for this URL" there is no politeness of the exchange.
I almost had a business trip to Japan some years back and people were discussing the formal and polite ceremonial business card exchange process with certain sequences of presenting, bowing, etc. I think learning about the cultural norms might be a key here with learning the language and the reasons why things are structured differently.
If you just want to get by for your holidays, sure just learn to translate with Duolingo. But if want to speak the language, you will just lose time.
I love Japanese. I love it so much that I (accidentally?) moved to Japan.
But it really has nothing to do with programming. It's a natural langauge with all the idiosyncrasies of natural languages. In fact I'd say that English in comparison feels like a man-made language purpose built for math and technology.
I am not suggesting that all languages are equally irregular, or illogical. But I do think that many times the differences are exaggerated.
So the colloquial patterns of use are pretty deeply dependent on understanding the rest of English, so you can notice where it becomes ambiguous or starts to feel like they could almost be different sentences but the person who is communicating with you is ignoring that because their personal dialect doesn't have those pauses and you kinda just have to deal with that when it happens.
Every other rule-set I've heard has to be accompanied by so many exceptions, and has so many competing schools that disagree, that they're just dogma, not description. And they're extremely hard to remember. So they're more about socially signaling that you're part of the well-educated upper-crust than they are about communication.
And yes, I'm an Oxford Comma user. It reduces ambiguity.
> The rule is that multiple adjectives are always ranked accordingly: opinion, size, age, shape, colour, origin, material, purpose. Unlike many laws of grammar or syntax, this one is virtually inviolable, even in informal speech. [0]
There is a proper order for adjectives in English that native speakers follow, but cannot explain.
> "It's an odd thing that every English speaker uses that list, but almost none of us could write it out. And as size comes before colour, green great dragons can't exist." [1]
0 - https://www.theguardian.com/commentisfree/2016/sep/13/senten...
As for why you need them, Wikipedia points out that because there's no concept of singular or plural (in general, excepting words like "私たち" for "we"), you may consider all Japanese nouns mass nouns. And with mass nouns in English you usually have to use something similar: ".. loaf of bread" ".. grain of salt". The "solution" is not the same in English as in Japanese (you still use "one, two, three.." in English), but still, you can't just remove it. For Japanese there are other ambiguities which are resolved by the counter system as well.
But yes, the counters.. that's one of the bigger stumbling blocks I ran into early on. Learned the numbers, yay! Then learned that I can't use the numbers when I want to say how many there are of something.. I limited myself to the few where I can, as in the counter for flat thin items like e.g. tickets. "にまいください"
You can do the same exercise as the author with almost all languages, the only small advantage of Japanese and more programming-like is the combination of kanjis to make up new words but even then the pronunciation might totally change. For example in Spanish:
"I eat beef" = "Yo como ternera" = subject + verb + object. Both in Japanese and Spanish, but not in English, you can omit the subject "yo"/"watashi". But this is so syntetic that people wouldn't use normally, I might instead want to say how good cow meat is and say "¡me encanta la ternera!" "Gyuniku ga suge ski!" (transliterated), in Japanese effectively eating up some random letters there.
Learning it is also kind of like learning physics in high school. After a few years you realise the first things you learn are a bootstrap to get started and not actually used in daily speech. Simple example: You hear the words "anata" ("you") and "sayonara" ("goodbye") one time in a month, but you will use them all the time in beginner Japanese class.
"I eat beef" is not something many native English speakers would say, or only in unusual contexts. We may say, "I am a beef eater" or simply "I like beef". Something about "I eat beef" as a statement conjures chest pounding imagery (it sounds primitive), so I'd propose we often pass through a sort of politeness filter too?
Anyways as a English only programmer, I don't know if I learned anything from the article - maybe you have to speak Japanese to get it?
(English grammar being simpler in this trifecta, but then in exchange you have the crazy pronunciation learning of English that I found out I would never "fully learn" and nobody really does in English, since you even have literal competitions (spelling bees) where people show off how good they are at it, and with jokes still happening between professionals like "is it 'data' or 'data'?").
Depends on the manga you read. There are plenty of manga revolving around everyday life, so called "slices of life" by the Western fans. I'd say they tend to use your regular everyday Japanese.
I said/meant that the Japanese learned at school, the one used by people everyday and the one at mangas are 3 different versions of the same language. I still do agree with what you say though.
I would assume it is similar to introducing a programmer to sentence diagramming in English. You start to see patterns and those patterns start feeling like a more formal system. Yet it always ends up crashing down and being too illogical to keep building upon.
One aspect that is likely at play is that learning a new language tends to be more formalized than one's understanding of their native language (outside of a sentence diagramming class or similar). When you learn a specific piece of grammar in a new language, you want to understand it formally. That means finding equivalent examples in a native language if they exist, or otherwise formally explaining the distinction between what grammar exists in a native language and the new grammar structure. I think this sort of pattern goes away when one approached fluency (unless they specialize in studying grammar itself in both their native and new language). The eventual goal is for grammar in the new language to feel as natural and yet illogical as grammar in the native language.
I even worked for a Japanese game publisher for a while (in their small US office, they originally invited me in to discuss maybe publishing a game I was developing that they spotted at Microsoft's XNAFest).
Spoke some Japanese phrases that everyone in the office did while there "Ohayoo gozaimasu!(good morning, as you arrive) Tadaima!(i've returned, said when you come back to the office, like after getting food or coffee) Shitsurei shimasu.(sorry for interrupting, say before enter someone else's office) Itadakimasu!(common saying before eating lunch, which we always did together) Hai, wakarimashita.(yes, i understand) Mmm, umai.(mmm, that food is tasty) Aa, so so so.(yes, i agree) Doozo.(please, go ahead)" are some of the most common examples I can remember from over a decade ago.
I also sat in some teleconference meetings conducted in Japanese with the parent company in Japan (I was pretty quiet, mostly just tried to follow general concepts and wrote down words I heard I was curious about to look up later). Even got to the point where I started saying 'Hai' instead of yes around others for a while, out of habit.
I lived in Japan for two years, and even tried to build an over-engineered learning tool (built a short roguelike version of Shortstraw algo to learn Kanji in Unity).
Fastest learning was in going to bars and talking to people when I lived there. Normal spoken Japanese is much more casual than textbooks. There is an introverted component to learning to read (drilling kanji, etc). that probably lends to a lot of tech solutions.
Japan simply has so many strong otaku (original meaning) subcultures to nerd on, anime/manga/game being the obvious ones (to be more accurate, manga in Japan isn't really a "sub"-culture, but the otaku portion of it is big enough on its own).
The only things I can think of that are comparable in the Western world are Star Wars or Sci-Fi in general, and Superhero comics. But I'm not super familiar with Western cultures.
But pronunciation of words that I've seen in writing for years but never said outloud before? God save me getting those right on my first or second or third try.
In comparison, Russian (my first language) and Japanese (a couple years of self-study + a couple more years of college classes) are a breeze in terms of figuring out the pronunciation (not talking about kanji here, assuming the reader knows proper furigana for whatever kanji in a word they are trying to pronounce). In 99% of the cases, it is pronounced exactly as it is written. If you know cyrillic alphabet, you can pretty much correctly pronounce every single word written in Russian on the first try (minus very few notable exceptions), even if you don't know anything else about the language at all.
And the exceptions tend to fall on such few very commonly used words, you usually nail them really quickly, and they sorta make sense. For one example of it in Russian, it would be "chto" (aka "what"). Very common word used all the time. But "ch" in it is more commonly pronounced as "sh", which feels rather natural in terms of how the mouth moves when trying to pronounce "ch" quickly in speech.
Note: however, Russian grammar is a hellhole of massive proportions compared to both English and Japanese. If you think that English is very free-form and flexible/messy in terms of sentence structure compared to Japanese (which I agree with), Russian grammar takes "free-form" and "messy" to another level.
Do explain!
I can watch full length videos on any topic from physics to philosophy to politics and understand nearly everything. But I have a hard time following casual conversations about small daily life things.
Further more, I can only think about programming and technology in English. If I have to talk about technology in Arabic (my native language) I basically have to think about it in English in my head then translate it to Arabic.
If you had learned Chinese (or Portuguese, or whatever) for your school material and computer science courses at university, you'd probably think it's Chinese that's "purpose built" for logic/math.
English seems to me a very illogical language, see for example the pronunciation rules compared to a more "logical" (pronunciation-wise) language like Spanish. Or Japanese, I hear, though I wouldn't know about that. Written English can feel similarly illogical very often.
When you’re at the cutting edge of research, it’s inevitable that you are going to have to come up with new words/language to describe new concepts, and so that process has been happening in English for decades.
It’s a fairly common phenomenon that languages assimilate words from other languages as new concepts are introduced by people who use that other language.
So I think it’s a bit of a stretch to say that English has some sort of superior utility for expressing scientific/programming concepts, at least not innately. It’s just that it’s more fleshed out after being used so heavily for such over a long time.
I also hate with passion that it's not written as it sounds (I think everyone who comes from a language with very regular pronunciation will tell you this) but I don't think this is a real issue on a daily basis.
On the other hand Spanish handles other things better. I'd say Spanish is a much better language than English to express feelings, specially anger.
Or are we saying that programmers are so one-dimensional that have to square any concepts into the round hole of programming?
I found that the main difficulties with Arabic were the sheer size of the vocabulary, and the fact that what is spoken is usually not written.
Japanese is in my opinion significantly harder (insane writing system, all words sound the same, lots of homophones, completely different sentence structure, very sophisticated social rules embedded into the language, etc). It feels a bit like reverse polish notation though!
I agree that in Japanese this is exacerbated by the Kanji system, where many words have the same (or very similar) sounds but completely different meanings, and the fact that most words at the advanced level are just two or three kanjis attached together and read in the supposedly "Chinese" way (aka the sound reading).
Having Arabic as a native language makes this even more difficult because in Arabic most of the time if words sound similar it's because they have the same root and are thus related in some way.
This is not a paid commercial or sponsorship. I haven't used the site in years.
But, the material at JapanesePod101 really bootstrapped my learning and helped me progress from beginner to advanced beginner.
The other thing that you can't do without is conversation with native speakers. In my case I went to physical language exchange meetups, but if you can find online ways to do it, that should work too.
The great thing about podcasts is you can listen to it while walking/commuting/etc.
To be quite honest it can be quite an overwhelming endavour, and it's very easy to think "f this I give up I don't care about this anymore".
Physiucal language exchange events help give you an "anchor" so that your learning has a purpose: you're meeting people and having positive social experiences with them.
You can tell by the word ordering. Japanese normally places the verb after the subject/object, but when a word of composed of two Kanjis, the verb comes first.
Example: 来店 coming to a store. 来 = come, 店 = store
In "regular" Japanese, it would be 店に来る "to come to a store". Not only is the readin completely different ("raiten" vs "mise ni kuru"), the word ordering is the opposite.
For the longest time the font rendering in Windows for example was absolutely garbage for kanji/hanzi on screens like most would be using and in that situation, and yes font size generally needed to be larger than it would be for Latin language users. While Windows technically worked for these languages it clearly wasn’t designed for them. This is somewhat fixed in newer releases.
On the other hand the text rendering on macOS has handled those characters considerably better at small sizes for the past couple of decades, which isn’t too surprising because macOS has aimed to replicate printed text with more accurate letterforms ever since OS X was released, as opposed to the pixel snapping technique used by Windows’ ClearType which only plays nice with Roman characters.
Linux/Freetype has been pretty good with Japanese/Chinese for the past decade too, ever since the improved antialiasing algorithm was added in.
HiDPI screens on smartphones, tablets, and laptops handle these characters pretty well regardless of OS because at those pixel densities, text rendering systems can usually render in adequate detail even at small sizes without doing anything special.
Next concept the author mixed is working with the verbs, verb.new(word.new("E", "A", "T")).PastTense() would give you "ate" Just like verb.new(word.new("食", "べ", "る")).Polite().Past() would output "食べました"
Then working with sentences, ex: Topic.new("me").toString() would be just "meは"... Put it all together and output everything subject > object > verb, instead of the more familiar subject > verb > object.
The author mixed a lot of those grammar concepts, with the words etymology... and it got confusing.
"2 kanjis becoming 1" is just the radical. 涙 (tear) 汗 (sweat) 泳ぐ (swim) 沈む (sink) 溺れる (drown), they all share the same radical (氵/sanzui/mizu/water). While it's not a rule, they are likely to have some relation to it. Just like in english waterfall, waterproof, waterspout, watermelon, etc.
I like the fact that the author is fascinated by the Japanese language and wants to share his discoveries. I guess everybody learning a seemingly completely new (unrelated to anything you know), experiences a similar phase. In his case he found similarities with a programming language. And I guess we all do that, we connect the things we're learning to the things we already know.
Someone learning english would probably be equally amazed by the watermelon. I mean... It's not so surprising if watermelon in your native language is, let's say: Melancia (portuguese). It takes half of the discovery surprise from you, as you already could suppose it's melon related.
I can't deny, "Fire + Mountain = Vulcan" was awesome to me as well. Learning that "Vulcan = god of fire in ancient roman mythology" does not hit me the same way, I already expect it to be greek/roman/latin.
ジェームズはダブリンに車で水曜日に行きました。 James-subject Dublin-to car-using Wednesday-on went. James went to Dublin in a car on Wednesday.
ダブリンに水曜日に車でジェームズは行きました。 Dublin-to Wednesday-on car-using James-subject went. To Dublin on Wednesday in a car, James went. In charge of words, Yoda was.
水曜日に車でジェームズはダブリンに行きました。 Wednesday-on car-using James-subject Dublin-to went. On Wednesday, in a car, James went to Dublin.
Similarly, specific to English, there is a definite order in which you have to place adjectives. You can pile up adjectives in front of a noun, but unless they're in the right order, they just don't sound right. "The big red balloon" works, "the red big balloon" is just wrong. As far as I know, Japanese does not have such restrictions.
So something the author has noticed, and as far as I know is correct, is that Japanese is a significantly more composable language than English.
Now I am more fascinated by contemporary China than contemporary Japan. I see that Japanese culture is based on much more ancient and broad Chinese culture. I also see a pick up in interests to learn Mandarin among my friends/coworkers.
I watched a few Chinese movies and I have to say they bring a breath of fresh air. I think whenever we want it or not we will see more Chinese media in the future, simply because they are different from what a typical person is used too. That makes them more interesting at least in the beginning.
It's popular among all types, very much so in the states and France due to anime.
But they export A LOT of culture. and they are very good at streamlining that export. Fashion, video games, anime, food, etc.
It's really no surprise it's popular. If you end up consuming the culture (as many of us did as kids) you will be attracted to the origins of it as it contains many elements of the culture you consumed.
But yes, there's a lot of cross over between "nerds" or "otaku" and Japanese culture exports.
I assume because they didn't fit into their home culture fully, so they found escape in another foreign one that was adapted for them, and thus found a community to share common interests with, which reinforces that "obsession".
tldr: you can nerd/otaku out on anything, but Japan makes some good stuff to nerd out on, so you get hardcore fans.
Coincidentally, it's exactly how I just distinguished them in English just now.
You can read ChatGPT's replies below (I manually collated the replies, leaving my prompts out):
In Japanese, mackerel is written as 鯖 (さば).
Blue fish" in Japanese is 青い魚 (あおいう お).
The middle character in "青い魚 (あおいうお)" is い, which is a form of the auxiliary verb "to be". In this case, it indicates that the noun "fish" (魚) is in a state of being "blue" (青い).
By using the auxiliary verb "to be", the phrase "blue fish" (青い魚) can refer to any fish that is blue, as opposed to a specific type of fish like mackerel (鯖). This helps to avoid confusion and allows for a clear distinction between different types of fish.
青い魚 is あおいさかな NOT あおいう お
The middle character has nothing to do with the verb to be; it's an adjective suffix.
青い魚 is literally "blue fish". It's not a full sentence.
い adjectives are said to have a built in copula, at least in material I've read, and since な in な adjectives is from the classical Japanese copula にある, one could surmise that い is also derived from a copula. As far as I can tell that is entirely wrong, but it is the kind of thing I wondered immediately after hearing that な and だ were derived from forms of ある.
Disclaimer: very little actual understanding of Japanese.
Is the main idea still correct? I'm curious what technique Japanese speakers use to avoid collisions like the one referenced in the article.
There's no technique per se. It's just the character size.
Example:
好 vs 女子
English and French work in the same way.
However roles are usually determined by word order. But in essence it's the same thing as obj.do_stuff(), 'obj' is the thing that do_stuff.
I've never really thought of programming languages in passive voice before, but it explains why I've increasingly written and spoken in passive voice structure even though I know it's "wrong" to do so.
movq %rax, %rbx
add rbx, rax
(cons a b)
a := b;
b 1 a + !Maybe I misunderstood you, but Japanese is neither of those - it's usually SOV, although could be OSV (and you can omit the subject or object sometimes).
Verbs are functions. In English, arguments are positional.
SUBJECT verb OBJECT.
I eat pizza.
But in Japanese they are named arguments with small helper words called particles. The subject uses 'wa' and the object used 'wo'. The convention is postfix in contrast to English's prefix notation.
Watashi-wa pizza-wo taberu.
With other verbs English uses named arguments too:
I go to the bank by car.
Japanese uses "e" and "de" for the arguments to this verb. Car is kuruma so "by car" becomes "kuruma-de".
Watashi-wa kuruma-de ginko-e iku
Obviously this is a massive simplification but I always found thinking about verbs as functions and the other words as named arguments to be very easy to understand.
(Edited for clarity)
I have a collection of python scripts you can use for text manipulation:
- regex:https://github.com/olsgaard/Japanese_nlp_scripts/blob/master...
- translitteration tables: https://github.com/olsgaard/Japanese_nlp_scripts/blob/master...
BTW this toy language came up in my search for the above: https://gist.github.com/typeswitch-dev/ac86d7e32167c1e5bf311...
http://web.archive.org/web/20110610231636/http://www.langmak...
While Forth has little point nowadays, RPN still is worth keeping in mind for combining direct manipulation with programmability in UIs.
It have noticed it usually sounds clunky in English, though it was a favorite of Latin and Greek authors. For instance, "Et lux perpetua luceat eis," is usually translated, "And may perpetual light shine upon them." But in Latin, the same root is in the subject and the verb. "And may perpetual light light them," is grammatical and (mostly) semantically equivalent in English. But it sounds clunky and looks like a typo :P
My uninformed supposition would be that it sounds clunky in English because English has less variation in word morphology, so the words are too similar when they have the same root.
For a moment the title got my hopes up.
I believe a language like that could be truly globalised without any cultural aspects