Hacker News new | comments | show | ask | jobs | submit login
The Logic Behind Japanese Sentence Structure (8020japanese.com)
41 points by tav 1 hour ago | hide | past | web | 5 comments | favorite





I learned Japanese very much the same way I learn programming languages and found it to be very easy to learn spoken Japanese.

As far as languages go, Japanese is structured a lot like a programming language. If you learn five or six "bunpo" or grammar rules, you can go a very long ways. Then, to improve, just learn add rules to your mastery.

When I first learn any programming language I start with basics: variable binding/assignment, types, conditionals, looping, etc. Japanese fits very nicely into the same learning method.

Does a language have if/then? is it 'if (<expression>) { expression }'? Or 'if <expression> then <expression> end if'? Is there an 'unless' form? What about 'else'?

For Japanese, it's <expression> naraba <expression>. Done Unless? <expression> nakeriba <expression>.

How about while? <expression> nagara <expression>

For people who can learn the gist of a programming language in a week, you could learn the gist of Japanese in a week or two. That doesn't mean you would be fluent. You'd still need to learn thousands of vocabulary words. But the basic mechanics can be mastered in days or weeks. More mechanics can be layered as needed.


I love how precise and detailed this article is written. If only more documentation were like this.

It was always my assumption that grammar is the most important thing to learn about a language. Vocabulary accumulates almost automatically over time, with practise (and a dictionary). Interesting to see how that holds in this case.


So I am sitting in Ebisu in Tokyo right now. I spend about 3-4 months a year here and have for about 8 years. My understanding of spoken Japanese is pretty decent. However it is by pure memorization over time. This just sorted a whole bunch of things out in my head as to the why. Very good stuff. Thank you.

This article resembles two different ways of designing protocols. In tcp [0], information are encoded in position, e.g. the first 16 bits are for source port and the next 16 bits are for dst ports. While in, say, FIX [1], information are encoding be delimiters and position doesn't matter.

[0] https://en.wikipedia.org/wiki/Transmission_Control_Protocol

[1] https://en.wikipedia.org/wiki/Financial_Information_eXchange


This year I've rediscovered my love for math, science, engineering and design. And now languages, human and computer. Excited for the next few months of growth!



Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: