News for hackers. Stuff that matters.

A comment on Synchronous Messaging at Mozilla: The Decision. Parent comment

Re:Synchronous Messaging at Mozilla: The Decision by dbrgn on Thursday December 19, 2019 @11:19AM (#21836230)
While I'm not happy with Discord either: Mozilla does not own Rust in any way, so they cannot decide what communication tool the Rust community uses.
[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by hu3 on Thursday December 19, 2019 @07:40PM (#21840787)
Every fulltime Rust developer is paid by Mozilla.

Saying Rust development isn't owned by Mozilla is more laughable than saying Go development isn't owned by Google.

[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by steveklabnik on Thursday December 19, 2019 @07:44PM (#21840808)
That’s not how governance works.
[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by wildfire on Thursday December 19, 2019 @09:16PM (#21841227)
Governance doesn't preclude the organisation which pays for the developers to have them do something else.

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.

[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by steveklabnik on Thursday December 19, 2019 @09:37PM (#21841322)
“We need x done” can’t be done at all until it’s approved by those who govern the project.

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.

[ Parent | on HN ]