This feels like a filler post. What can we usefully learn about a browser that's over a year away from an alpha release?
this post was submitted on 24 Nov 2024
81 points (87.2% liked)
Linux
8178 readers
368 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 1 year ago
MODERATORS
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,
I think I need a little more help here. Maybe it's just about not having English as a native language, but the link talks about avoiding the word bug because of connections to sodomy?
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.
"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