I read Japanese (I think this is Japanese in this case - it just happens to use a subset that is also Chinese - maybe).
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.
Posted by markburns on Jul 19, 2015, 11:05 PM
Tags
Related issues
- > someone has made the wrong editor choice Just the other day I made this comment on the topic of "nvim vs emacs", I think it fits here ...
- GLES isn't a bad way to teach graphics but I wish there was a middle ground between it and VK.
- > [Edit: note that the above video is "content" so if you're not used to the style it might be offputting but I'm into it] I hate that i...
- And thats why its a large language model not a large skin cancer recognition model or large creative thinking model I hate that people th...
- I hate that this article is talking about Photocraft killing Photoshop because of AI as though Ivan Kutskir didn't build Photopea years a...
- That's a fair complaint, but for the most part that only applies to the faces (which would be an absolute nightmare to hand animate in sy...
Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments
complaint (Other)
> someone has made the wrong editor choice Just the other day I made this comment on the topic of "nvim vs emacs", I think it fits here ...
NewGLES isn't a bad way to teach graphics but I wish there was a middle ground between it and VK.
New> [Edit: note that the above video is "content" so if you're not used to the style it might be offputting but I'm into it] I hate that i...
And thats why its a large language model not a large skin cancer recognition model or large creative thinking model I hate that people th...
I hate that this article is talking about Photocraft killing Photoshop because of AI as though Ivan Kutskir didn't build Photopea years a...
That's a fair complaint, but for the most part that only applies to the faces (which would be an absolute nightmare to hand animate in sy...
I wish there was something that could be done beyond feeling powerless.
I don’t hate taxes per se but I hate that the government will take tax dollars earmarked for one purpose, which is how they got the tax a...
I read Japanese (I think this is Japanese in this case - it just happens to use a subset that is also Chinese - maybe).
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.
Comments (0)
No comments yet. Start the discussion.