I read Japanese (I think this is Japanese in this case - it just happens to use a subset that is also Chinese - maybe). This code is definitely easier to parse

I read Japanese (I think this is Japanese in this case - it just happens to use a subset that is also Chinese - maybe). This code is definitely easier to parse visually for me. It's really satisfying. As a character set, it is much more information dense, it just requires a lot of upfront study making it less efficient in the short to medium term (~10 years or so). However, I would hate to work on a codebase like this. It is a key press to switch between input methods (languages), or a key combination on different keyboards. When combining this with vim I find it incredibly frustrating to type. You have to mentally keep track of which language you are in, as well as which vim mode you are in, 4 options instead of 2. Plus you have to be in English language mode for vim commands to work correctly. Although it is true that you spend more time reading code than writing code, it would obviously exclude those that don't read Japanese. It would be a nice-to-have to be able to have Japanese variables only for the reading phase of a project when you are getting up to speed. Then swapping them out for English words when editing. Can't see how it would work in practice and a really limited market too. But yeah, it's satisfying to look at.