Live data from Hacker News

End of Japanese community

support.mozilla.org

251–260 of 820 posts

Re: End of Japanese community

#251
It's funny how Japanese contributors often go nuclear whenever things don't go their way instead of communicating etc. Bugs happen. this is tech. open communication is always the way to go before escalation. we see the same phenomenon in git, ruby etc etc etc.

Ironically, Japanese work culture encourages over-communication. It seems that open-source is considered a counter-culture that they want to escape japanese work culture from.

Re: End of Japanese community

#252
> Hi Marsf,

> I'm sorry for how you and the Japanese community feel about the MT workflow that we just recently introduced. Would you be interested to hop on a call with us to talk about this further? We want to make sure we trully understand what you're struggling with.

> My timezone is UTC+7, so it should be easier for us to set up time. Let me know how that sound!

What a horribly condescending and patronising response. If I'd received this it would just further vindicate my decision to quit.

Re: End of Japanese community

#253

Earlier quoted context omitted.

I'd just begin again in a golden land of opportunity and adventure: https://ladybird.org/#gi

I'm happy that somebody is trying to create a new browser -- even though some people say it's impossible nowadays. But FUTO sponsoring that project gives bad vibes.

Why? You’re referring to tue club that makes Immich, right? What’s so bad about them?

Re: End of Japanese community

#254

Earlier quoted context omitted.

I edited my comment to clarify I hope. Imagining what it could have done wrong and knowing what it did wrong are different.

Do you expect someone who has just watched a bot replace 20 years of their work, with no prior consultation or review, to now write a detailed post about how translations by the bot are not specifically wrong? The core issue here is the way the bot was deployed. The fact that they had the poor taste to make it auto-replace articles written by their own volunteers is idiotic and disrespectful in the extreme. A new bot…

This is Mozilla as usual, arrogant and tone deaf.

Re: End of Japanese community

#255
post #20

Earlier quoted context omitted.

The third, more likely option is that it was a careless act. Clearly a mistake in any case.

What's the saying? > Never attribute to malice that which is adequately explained by stupidity.

At some point the rate of stupidity becomes suspicious again.

Re: End of Japanese community

#256
post #101
post #72

Earlier quoted context omitted.

I can imagine what you mean, but since I am not in Japan, it would be interesting why you feel that way.

long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset. So you move slowly and end up having very annoying conversations and compromises instead of just pushing something through. And the formal process is just a formality anyways, so then anyone not in the informal chatter just gets to experience the capriciousness anyways The sort of consensus…

> long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset.

How do you know what "the right thing" is at the outset without talking to the stakeholders?

I'm dealing with someone's "the right thing" that is actually wrong and dumb. They didn't ask us before rolling out the new "standard."

Re: End of Japanese community

#257

Earlier quoted context omitted.

Those would be the guidelines that all translation contributors are expected to follow, which are given to all prospective translators. It sounds like Mozilla just turned on the machine without consulting the human translators to see if the machine actually worked in a useful manner.

> It sounds like Mozilla just turned on the machine without consulting the human translators to see if the machine actually worked in a useful manner. Yes. And someone should make a real apology. But learning what the machine did wrong is part of fixing a machine.

An apology? Mozilla is incapable of taking responsibility. What they will do is blaming someone else, probably the translators.

Re: End of Japanese community

#258
post #29

It’s a shame because “improve an off the shelf llm ti translate in line with this large dataset we prepared” is precisely the kind of project people love to work on. It could have been a chance to immortalize the hard work they did up until now.

> this large dataset we prepared

You mean the two+ decades of labour of love was always done to be a nameless contribution to the AI machine? Somehow I think he would have picked another hobby if he had known that back then.

Re: End of Japanese community

#259
post #101

Earlier quoted context omitted.

long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset. So you move slowly and end up having very annoying conversations and compromises instead of just pushing something through. And the formal process is just a formality anyways, so then anyone not in the informal chatter just gets to experience the capriciousness anyways The sort of consensus…

> long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset. How do you know what "the right thing" is at the outset without talking to the stakeholders? I'm dealing with someone's "the right thing" that is actually wrong and dumb. They didn't ask us before rolling out the new "standard."

Some people are very confident in their understanding of a problem! Others will discount the validity of the stakeholders involved having good judgement.

I think most people have at least one issue where they discount one of the stakeholder's judgement, it's all fairly contextual. But hey, if you're the CEO of some company you have the ability to act on that discounting.

Re: End of Japanese community

#260

> I'm sorry for how you and the Japanese community feel about the MT workflow that we just recently introduced. Would you be interested to hop on a call with us to talk about this further? We want to make sure we trully understand what you're struggling with. Talk about being tone deaf. This was so incredibly rude. No consult, no request whether they wanted this or not. Mozilla keeps finding new ways to shoot itself…

sounds like it's almost an AI response? I can't believe a person responds that way

AI wouldnt misspell “truly”. It’s a human.
Post reply on HN