In this article, I would like to introduce a new web browser called Ladybird. This ambitious open-source project aims to revolutionize the browsing experience. Although it hasn't been officially...
My first impression was the lead developer calling a PR for gender neutral pronouns in the documentation “personal politics”. Pardon me if I’m still underwhelmed, no matter the state of the project.
Some made a pull request with all the changes made already. The issue that the PR addressed was the excessive use of he/him in the docs when referring to developers (aka the person reading the docs). Contributors expressed that they didnt think using male only pronouns in the docs made much sense when referring to any developer reading the docs. This wasn’t some entitled person trying to force the ladybird dev to rewrite the docs, all they needed to do was merge the changes.
In this scenario, I think the pronouns should be changed regardless of the gender of the devs. Here’s a screenshot of the suggested changes, which are quite minimal. The reason why I think this should be changed is because this is in the build instructions for a project that many devs are needed. Hence, they should at least be open to discussion rather than shutting it off completely. And honestly, this is a small change. Their reaction to this made it more political than the commit itself, and honestly the commit was not political in my mind. Their reaction also demonstrated how they respond to contributions, and an ambitious project like this will need a lot of contributors. If their leadership keeps this up, it is very off-putting for people to collaborate with them.
My first impression was the lead developer calling a PR for gender neutral pronouns in the documentation “personal politics”. Pardon me if I’m still underwhelmed, no matter the state of the project.
Ohhh,
The name of this browser, and this commit, that’s definitely a no go concerning me.
There is enough as**oles like this,
Honestly the name was enough for me but seeing the commit discussion certainly makes me feel justified for judging a book by its cover.
That’s disappointing.
Guess they have more important matter to attend.
Some made a pull request with all the changes made already. The issue that the PR addressed was the excessive use of he/him in the docs when referring to developers (aka the person reading the docs). Contributors expressed that they didnt think using male only pronouns in the docs made much sense when referring to any developer reading the docs. This wasn’t some entitled person trying to force the ladybird dev to rewrite the docs, all they needed to do was merge the changes.
I think a bit more context could help here. What if those devs are male and prefer he/him? Should those pronouns be changed?
In this scenario, I think the pronouns should be changed regardless of the gender of the devs. Here’s a screenshot of the suggested changes, which are quite minimal. The reason why I think this should be changed is because this is in the build instructions for a project that many devs are needed. Hence, they should at least be open to discussion rather than shutting it off completely. And honestly, this is a small change. Their reaction to this made it more political than the commit itself, and honestly the commit was not political in my mind. Their reaction also demonstrated how they respond to contributions, and an ambitious project like this will need a lot of contributors. If their leadership keeps this up, it is very off-putting for people to collaborate with them.
based
bAsEd 🤡