I know the recent reactions from Japanese community to dev.to; I am one of them.
This is a really interesting topic. With dev.to, we're aware that English is the dominant language in programming, but not necessarily the language programmers actually speak in. With that in mind, we're building out features which will allow for more easily segmentation between languages so that, say, Japanese articles can fit in more naturally within the architecture of the site.
Speaking about dev.to, my concern is that Japanese people often break the convention inside the community. They think their common sense is the common sense for entire globe.
For example, StackOverflow has recently released their official Japanese version. Japanese people were very much pleased by this news. The 'official' Japanese support of ja.stackoverflow was not quite pleasant (for me); people write tech-related Q&As in obsolete communication style.
The way they write questions inside ja.stackoverflow looks very similar to the way they ask questions to their boss. They even 'feel sorry' for asking questions and consuming people's time for writing answers.
I don't wan't to see this Japanese nonsense. Not in platform like dev.to. I understand the importance of internationalization, but I hope that this kind of tragedy is not going to happen.
Well thanks for the feedback. It's really valuable. I hope we'll be able to offer settings and personalization that lets everyone communicate in the styles and subcommunities of their choices. This is why we move methodically on this sort of thing. We have a lot more flexibility in our implementation than Stack Overflow, which should help guide the future.
Disclaimer: I'm a Japanese programmer and I like ja.stackoverflow.com (ja.SO) very much.
Let me make a small correction. From a viewpoint of ja.SO's policy, the writing style of questions doesn't matter; the important point is how those questions are useful in the future. Although Japanese people often ask a question in the "feel-sorry" (or polite) style, the ja.SO community does not force people to do so. We can post both an "obsolete"-style question and a non-"obsolete"-style question, unless it's too rude. It's not an important problem for ja.SO.
I'm sad to hear that you don't like such a style. Originally, the purpose of opening ja.SO was to ask a question in Japanese language (ref). Then, it's inevitable that there're many obsolete-style questions, because it's a kind of Japanese culture. Japanese language is, you know, spoken only in Japan in contrast to English, which is used all over the world. So I personally think that Ben's proposal (preparing subcommunity options) is good for diversity in dev.to. In fact, this is what SO did.
I admit that Japanese programmer (including me) should learn English more and more, but I think the ja.SO's problem you pointed out is a bit different from that.
(FYI, there is a continuing discussion on ja.SO's chat (in Japanese).)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Glad to see the real world opinion from the dev.
I know the recent reactions from Japanese community to dev.to; I am one of them.
Speaking about dev.to, my concern is that Japanese people often break the convention inside the community. They think their common sense is the common sense for entire globe.
For example, StackOverflow has recently released their official Japanese version. Japanese people were very much pleased by this news. The 'official' Japanese support of ja.stackoverflow was not quite pleasant (for me); people write tech-related Q&As in obsolete communication style.
The way they write questions inside ja.stackoverflow looks very similar to the way they ask questions to their boss. They even 'feel sorry' for asking questions and consuming people's time for writing answers.
I don't wan't to see this Japanese nonsense. Not in platform like dev.to. I understand the importance of internationalization, but I hope that this kind of tragedy is not going to happen.
p.s. I've added the #meta tag for this post.
Well thanks for the feedback. It's really valuable. I hope we'll be able to offer settings and personalization that lets everyone communicate in the styles and subcommunities of their choices. This is why we move methodically on this sort of thing. We have a lot more flexibility in our implementation than Stack Overflow, which should help guide the future.
Disclaimer: I'm a Japanese programmer and I like ja.stackoverflow.com (ja.SO) very much.
Let me make a small correction. From a viewpoint of ja.SO's policy, the writing style of questions doesn't matter; the important point is how those questions are useful in the future. Although Japanese people often ask a question in the "feel-sorry" (or polite) style, the ja.SO community does not force people to do so. We can post both an "obsolete"-style question and a non-"obsolete"-style question, unless it's too rude. It's not an important problem for ja.SO.
I'm sad to hear that you don't like such a style. Originally, the purpose of opening ja.SO was to ask a question in Japanese language (ref). Then, it's inevitable that there're many obsolete-style questions, because it's a kind of Japanese culture. Japanese language is, you know, spoken only in Japan in contrast to English, which is used all over the world. So I personally think that Ben's proposal (preparing subcommunity options) is good for diversity in dev.to. In fact, this is what SO did.
I admit that Japanese programmer (including me) should learn English more and more, but I think the ja.SO's problem you pointed out is a bit different from that.
(FYI, there is a continuing discussion on ja.SO's chat (in Japanese).)