GitHub - LadybirdBrowser/ladybird: Truly independent web browser
-
Try out SearXNG.
-
It can also be the correct arrestment. Context is everything.
-
Totally excessive in view of the facts.
There are so few alternative browsers and the collapse of the privacy is so global. That seems to me a minor point in relation to the goal.
-
i know there was a thing at the beginning of the project where they wrote a lot of the documentation with masculine pronouns (ie assuming the reader was male), and when they were asked to change that for gender neutral pronouns, they said no because "they don’t want politics in their project"
beyond that however, idk if they eventually changed that or if they did other stuff
-
Sigh, you do have a point.
Maybe this was by a different reviewer, idk.
It was. Some other member of SerenityOS, not the person behind Ladybird (awesomekling).
blog author should be more accurate (see above)
That's fair. I'll say though, the blog post is dated from 1 day after the PR was actually merged. It's not unreasonable to think that, when they wrote it, it really hadn't been merged and they only saw the initial denial citing the policy.
He may be. Idk.
Yeah, I was just trying to say that that wasn't the point of my rant. I get it I get it.
-
I donate to Ladybird and Servo, and I hope they succeed. We need serious competition and a check on Mozilla (not to mention Chrome and Safari).
That said, I'm sad that neither Ladybird or Servo are licensed under strong copyleft licenses. We need user-oriented browsers now more than ever, and strong copyleft enables that. I worry that, even if these engines are successful, they will be co-opted by proprietary browsers and eventually superseded by them.
This happened before - both Chrome and Safari ultimately derive from KHTML, Konqueror's browser engine. If KHTML had been licnesed under the GPL instead of the LGPL, Chrome and Safari may have been free software today (or at the very least, it would have been much more difficult for Apple and Google to get started).
That said, I wish Ladybird the best. There donation = no influence policy is excellent, and I really, really hope they can stick to it in the long term.
-
Don’t think we should be scared of the word “political” or “ideology”.
-
in my mind it's kinda the point of Ladybird to have a permissively licensed implementation of web standards, I like permissive licenses if only because they reduce legal risks
-
It’s not unreasonable to think that, when they wrote it, it really hadn’t been merged and they only saw the initial denial citing the policy.
That never happened on this PR. The only human reply before the merge (aside from the submitter) was this:
Please fix the commit messages (see BuggieBot's comment); and maybe this can go in one commit? Doesn't really need to be 5 separate ones.
And this is BuggieBot's comment:
Hello!
One or more of the commit messages in this PR do not match the SerenityOS code submission policy, please check the lint_commits CI job for more details on which commits were flagged and why.
Please do not close this PR and open another, instead modify your commit message(s) with git commit --amend and force push those changes to update this PR.It's a completely different.
This, plus the tone of the blog post looks like they were on a crusade instead of trying to accurately portray events.
Sorry to beat a dead horse here, my point is that we all need to be careful jumping to conclusions, especially in FOSS where discussion almost exclusively happens asynchronously in text and with people with different backgrounds. Pretty much everyone involved failed at that.
-
And this is BuggieBot’s comment:
Yeah I was referencing that comment.
Sequence of events:
- PR trying to change pronouns.
- Automated response citing policy.
- Author takes note of it for blog post.
- PR fixed and merged.
- Blog post published.
Precocious, certainly, and I agree it was misguided. The blog post was indeed emotionally motivated, that's more than clear.
Sorry to beat a dead horse here
It's alright. I think these discussions need to be had.
-
Right, but the policy was commit hygiene (lots of small commits), which has nothing to do with the "no politics" policy. It's right there in the comment, and the suggestion is to squash the commits into one.
It’s alright. I think these discussions need to be had.
Agreed. And unfortunately, I felt it necessary to be really wordy to not come off as supporting intolerance in any way, while still arguing that I would've done the same (reject 1-line cosmetic PRs).
This is some kind of correlary to Poe's Law, or perhaps Godwin's Law.
-
Right, but the policy was commit hygiene (lots of small commits), which has nothing to do with the “no politics” policy. It’s right there in the comment, and the suggestion is to squash the commits into one.
Suspiciously close to what Hitler would say... /s
-
Isn't servo mostly a Mozilla-led project? I thought servo would probably just replace gecko as the engine firefox used if it ends up succeeding
-
Lol, got me there.
Hitler would probably be a formatting Nazi too. Can't have that <insert slur> extra whitespace.
-
Iirc it started its life that way but Mozilla abandoned it and the community picked it up
-
Yep, I understand but disagree. Maybe it comes from working with so many ESL coders, but I'll happily accept typo corrections because it's not always obvious what words should be if you're not steeped in the culture.
-
It really depends on the project.
If you're a larger project, you can see a ton of these from people hoping to land a commit to put "contributor to X" on a resume somewhere. Those add up and are really distracting and possibly automated. They waste everyone's time, especially if they spawn a bunch of conversion like this did.
If you're a smaller project, it doesn't matter as much. I work with ESL coders too, so I get it (1/4 of my office is ESL immigrants, and ~2/3 of the broader team is ESL). I fix comments all the time, I just include them with other changes.
So it depends. But in general, a high profile project should reject this noise to discourage this behavior.
-
Alright, read up on it a bit more. Sadly the language choices (C++ now, maybe Swift later) rubs me the wrong way for something that needs to be incredibly secure against attacks. I really really support additional browser engines, but likely not this one.
Thus I think Servo is a better choice for those looking to contribute. IMHO.
-
because a turn key platform they don’t have to self host and maintain frees them up to do the work.
