This feels like a filler post. What can we usefully learn about a browser that’s over a year away from an alpha release?
The article sucks, but not because it’s about early stage software. I’d love to get a deep dive on its architecture and how it would differ from the other browsers
I tried two months ago when people were talking about it, and I learned the reason why they said it’s going to take years for the first release. Honestly I am pessimistic about the browser situation these days, but best of luck
I think trying to do a “modern web browser” which is almost like a whole OS, is the wrong path to take. To retake the internet, we need to return to the basics. A simple web browser that does, at best, HTML and CSS. Heck, maybe even Gopher / Gemini support. No javascript, no worry about code execution, no “dynamics”. Much easier to develop and maintain, and promotes a leaner and safer internet.
Now, be it a hobby project or some sort of, by miraculous intervention, cleaned-up Mozilla, that I leave to the peoples.
Might come along just in time for when Mozilla pulls the plug of Firefox and ends up just using a rebrand of Chrome.
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,
With you in that the sexist comment means avoid, but am I missing something about the browser name? Aren’t ladybirds just what ladybugs are called in the UK?
https://www.natgeokids.com/uk/discover/animals/insects/ladybird-facts/
Etymology my friend, etymology,
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.
I’m usually in the camp that people should just speak as they like, but using they is just a really natural thing and non invasive in the English language. That’s a change that makes sense. They in this position might also refer to an organization, it Abstracts the entity using the thing away, which makes sense.
based
bAsEd 🤡
“first alpha release is expected ~16 months from now”
“First Impression: I was not impressed”
You don’t say
Stupid name. Branding will not help this browser.
The name is fantastic, however the logo looks pretty cheap, the previous one (used on SerenityOS) was much better and unique.
Yeah, it needs to be called xxxShinybugOfFIREEEEExxx or something because then it would sound like every other browser but with edginess up to 11 /s
