Steve Klabnik will predictably reply to me saying that it was the decision of the community and blah blah, but the Mozilla Corporation should not have allowed it.
Baiting people like this is inherently uncivil.
> the Mozilla Corporation should not have allowed it.
Mozilla has no say over what the Rust community does.
Saying Rust development isn't owned by Mozilla is more laughable than saying Go development isn't owned by Google.
Goverance: We should complete the async work before we do X
Pay master: We need X done. Do the async work later.
i.e. the person who is paying the money gets to set the priority.
Actual example of this: years ago, the Servo team really would have liked a form of inheritance, to help with DOM stuff. We thought it wouldn’t be right for the language. Rust still doesn’t have inheritance today.
This argument is also predicated on the idea that full time devs get more done than part time ones do. That’s true in a one on one comparison, but there are far more part time ones, so collectively they do way more work.
[0]: https://www.rust-lang.org/what/networking [1]: https://www.rust-lang.org/ [2]: https://prev.rust-lang.org/en-US/
But I do not think it is up to Mozilla corporation to pick communication platform for Rust, that is not their job. The blame lies squarely on the Rust project.
Do you see the problem with that line of thinking or do I have to explain further?
Almost all of Mozilla is under Moco.
I could go my own way and comment for free (as I already do) and then I would be able to do whatever I wanted.
But as long as I am funded by you, yes I should do what you ask of me.
I suspect they might move back to Mozilla's Riot/Matrix instance once it's set up in production, but that hasn't happened yet.
In general, the teams are allowed to organize themselves as they wish.