Live data from Hacker News

Japanese explained to programmers

lajili.com

151–160 of 416 posts

Re: Japanese explained to programmers

#151

Honestly its really tiring to see people promoting the rote-learning of Kanji. 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…

I have often thought that people who advocate anything but rote-learning of English spelling are misguided. I know that phonetics are a popular myth in English.

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.

Re: Japanese explained to programmers

#152
post #16

Earlier quoted context omitted.

A very important distinction which textbooks often fail to explain clearly. The subject is always and only が. Even if there's no が in the visible sentence.

Not sure if I understand this invisible が idea. Where is it in「私は牛肉を食べます」?

There’s nothing to understand. It’s not a thing.

Re: Japanese explained to programmers

#153
post #145

Earlier quoted context omitted.

But what is a language without its written form? 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 infl…

I know a person who is fully fluent (I should write "proficient") in Japanese, he has lived in Japan for decades. Built a successful career. But he can't write Japanese. He doesn't read Kanji. Sounds almost incomprehensible to me, because I learn languages by reading (which is where Japanese has given me some trouble). As for English.. "I is to town goes". Mess it up in every possible way and the meaning is still the…

This is not uncommon for the children of Japanese people living in the West, particularly when they have married non-Japanese. They pick up the spoken language via osmosis but the written language…not so much. It is, as I said, very hard and cannot be mastered without extensive study. Many of these hafu, as the Japanese refer to them, nonetheless enjoy successful careers in Japan, presumably usually in environments that don’t require them to read anything.

As to your English example, it…doesn’t really work? There are languages that aren’t dependent on word order for their meaning, but English - shorn of the grammatical signifiers retained by many of its brethren - is not one of them. Latin is famously largely order-independent; another topical example would in fact be Japanese! Its particle-based system for annotating subjects and objects mean their position is unimportant; the only real requirement is that the verb comes at the end.

Re: Japanese explained to programmers

#154
post #79
post #70

In case anyone is curious, I asked ChatGPT how Japanese refer to "fish that are blue" since "blue fish" is also the word for mackerel. 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 "…

ChatGPT's response is full of BS. 青い魚 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.

It's so weird. I know Japanese and I know chatGPT mostly confidently wrong. But still I wanted to believe it and give it the benefit of the doubt. I was wondering if fish had another pronounciation in addition to sakana.

Re: Japanese explained to programmers

#155

By far the hardest language I've ever tried to learn. In addition to pissing my Korean girlfriend off, it was so difficult I dropped the class after 2 weeks or so. 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...

My understanding about Chinese is that what makes it hard for English speakers is that it’s a tonal language. Hearing the tones at all, and even more so reproducing them, can be very hard for many English native adults.

Re: Japanese explained to programmers

#156

Earlier quoted context omitted.

Because of its exactness. Like with words like course coarse mussel muscle altar alter idle idol very vary presents presence, etc. /s

I know you're being sarcastic, but as a Spanish native speaker I'd say English precisely excels on how well it handles ambiguity and certainty. 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…

> I'd say Spanish is a much better language than English to express feelings, specially anger.

Everyone says this about their mother tongue. True mastery of a language is comfortably being able to call someone a c**t in it in the heat of the moment.

Re: Japanese explained to programmers

#157

Earlier quoted context omitted.

I know you're being sarcastic, but as a Spanish native speaker I'd say English precisely excels on how well it handles ambiguity and certainty. 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…

I think you have to go to English vernacular, "as she is spoke" to express especially anger. An angry Dubliner or someone from the midlands for example :-)

The Glaswegians would like a word…

Re: Japanese explained to programmers

#159
post #108

Earlier quoted context omitted.

Indeed, my interpretation is also that the subject can be expressed by any of は, が, or the context. I am having trouble understanding the "implicit が" analysis because it seems to me that in many cases adding a が would make the sentence nonsensical (like in the example.) So it just feels like retrofitting が into a role that it really doesn't have. Then again, I'm not an expert, so I may very well be wrong about this.

That's why it's called a zero-が if there's no "が", because every valid Japanese sentence needs a subject. It may sound like nitpicking, but it's important to clarify that it is not correct to say that "the subject can be expressed by any of は、が, or the context". Thinking about it that way only makes it difficult to understand where the particles should be used, and indeed the difference between は and が. Either the su…

> It may sound like nitpicking... [snip]

You're entirely right, what I said there was incorrect (or sloppy at best.) Thank you for the correction.

> That's why it's called a zero-が if there's no "が", because every valid Japanese sentence needs a subject.

This is the part which I find unhelpful. You could say "every valid English sentence needs a subject and a verb", and you'd be having a hard time finding a sentence in e.g. the U.S. constitution that doesn't explicitly contain a subject and a verb.

But in Japanese, not every sentence needs to specify the subject. Every sentence still has a subject, because the definition of a sentence is "a subject and a predicate", but that applies to every human language.

The problem then is that the "zero-が" then feels like bolting a potentially ungrammatical (or at the very least unnatural) construct onto every sentence to explain the simple fact that yes, indeed, Japanese sentences do have a subject, but it's often unspecified. It also misses the important point that が, by clarifying the subject, also has the role of emphasizing it, which changes the meaning of the sentence.

To go on a bit of a tangent, Hungarian has a similar problem. It also frequently omits the subject, and specifying it also changes the meaning of the sentence:

* Lefekszem. =I'm going to sleep. (The subject is already specified by the conjugation.)

* Én lefekszem. =It's specifically me, who is going to sleep. (For example, you are asked if you're going to the after-party, but in contrast to others, you're tired and want to sleep.)

You could add an "implicit én" to the first sentence, to show that yes, it indeed does have a subject. Maybe it's helpful for people whose native language can't just omit the subject. But it subtly changes the meaning, so ultimately I don't think it's very good analysis, but rather "translating into your native language."

As I said, I'm not an expert, but I hope what I'm saying makes sense.

Re: Japanese explained to programmers

#160
post #42

Honestly this feels like "programmer circle jerk" material. 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.

My suspicion is it is a bias to one’s mother tongue. I feel the same way about Arabic. English feels “lawless” and “undeconstructable” in some cases, no equation for “creating” words that works every time. In this sense Arabic is way more “Mathematical “ to me although all the number theory, graph theory, discrete math etc. books I’ve read are written in English.
Post reply on HN