Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

This Month in Ladybird – August 2026

ladybird.org

Post reply on HN
Print view View original

51–60 of 86 posts

Re: This Month in Ladybird – August 2026

#51

Post by charcircuit »

_jackdk_ wrote: post #12
sho_hn wrote: post #3

Earlier quoted context omitted.

> Ladybird seems to have received a nice boost in momentum in the past two years. I'm still very interested in the project and look forward to each monthly update, and I can empathize (though not agree) with the reasoning, but something is off ever since they announced the decision to close the project to outside contributions. It's still Open Source, but only a self-selected group of maintainers gets to write and me…

I agree with your concerns but also think that a new viable browser engine will be such a benefit to the health of the open web that I'm willing to overlook such irregularities, at least for now. sqlite doesn't accept contributions either and it's done well for itself, and if Ladybird ends up going sour there's always the possibility of a fork. This is similar to my stance towards Firefox: despite the actions of Mozi…

Multiple browser engines reimplementing the same things fragments engineering resources and blink based browsers do have working as blockers. In fact ladybird uses the same adblocker as Brave, which is blink based.

Re: This Month in Ladybird – August 2026

#53

Post by ilvez »

senfiaj wrote: post #26

I am watching this project with interest. It's impressive that they're doing such titanic work. However, I'm highly skeptical that they can create a real rival to established browsers. I'm sorry for telling this, but Web standards are simply too complex and huge. Ladybird to Chrome / Firefox is almost like Wine / ReactOS to Windows, that last 3-5% of gap actually differentiates a normal browser from a browser that is…

Just a small personal touch -- my coworker is constantly pushing me to use Chrome because it "just works", but I'm stubborn as hell. Used Firefox from early 2000s. Oh how I will love to twist his nerve even more once I will switch to Ladybird. Saying this because there has been more harder days to counter these pushes. And to be honest I think we are overthinking about how much this last 3-5 % actually matter for huge crowds.

I understand that your argument still stands in big picture, but in this big world there is plenty of room for Firefox and Ladybird and there is more than enough room to grow. Firefox mostly is being held back with their organization. I'm not convinced that it is technical problem.

But then again, I'm still believing that there will be a year of desktop Linux coming. Maybe even sooner than we expect.

Re: This Month in Ladybird – August 2026

#58

Post by dainank »

dotinvictim wrote: post #54

[flagged]

On a serious note, it would be nice if in the far far future, once the browser is very stable, they release a windows binary since I do sometimes still use Windows 11 for moments when it is needed and it would be a shame to then temporarily still have to switch to Edge e.t.c. instead of being able to use Ladybird there too.

Re: This Month in Ladybird – August 2026

#59

Post by vivzkestrel »

few stupid questions as always so that i can become a smarter person

- what is the process of making a browser engine? what does the requirements look like

- how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated

- how is backward compatibility implemented?

- is all the code written in c++ or is it rust these days?

- how many people in a team do you need and how long would it take to write a browser engine from scratch

- what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not?

- how is mobile vs desktop handled at the browser engine code level?

Re: This Month in Ladybird – August 2026

#60

Post by throwa356262 »

vivzkestrel wrote: post #59

few stupid questions as always so that i can become a smarter person - what is the process of making a browser engine? what does the requirements look like - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many peo…

For the first two, I highly suggest you watch a few of their videos from about a year ago.
Post reply on HN