When it comes to larger projects, first:

- you don't need to understand the whole in order to help

the kind of bugs you can start with are like :

- this icon is a bit weird, it's off centre by 2px - how do I add 2 pixels to this icon? either by moving it or by changing the underlying image asset? if I'm moving it, what is the subroutine that paints it? if I'm changing the image asset itself, where is it stored? (is it in a packed store? or is it just a plain file, etc)

- when I click this button, trace the pathway - it's supposed to add to history and turn blue. is it doing that?

etc.

For large projects, start super small and work your way out from there.

>Last time I tried, I couldn't find a website that worked with it.

That was the case for me last time I tried it as well, which was a few months ago. Tried it again yesterday and I could load many pages. Could even render complex real life pages like YouTube.

I recommend anyone to build it themselves. It is a very simple and smooth experience.

Pick a site that almost works on it and then fix it to fully work?

You don't have to implement some big new feature. I found a layout rendering problem when I tested it on my own website and could quite easily go and fix it without having any prior experience with browser development.

English isn't my first language; sorry about that :)

Why the tone policing? This isn’t helpful. Whereas parent comment was to the point and linked to a helpful resource. Give people the benefit of the doubt and assume good intent.

I love Rust, but I do not like how people are rust evangelists and look down on everything else. That is not how we in the Rust community look at things.

Now, with that out of the way. Andreas has been very clear about the reasons why C++ is the chosen language. He has years of experience with it along with writing browsers.

Im paraphrasing here, but he has said that the web evolved around the era of OOP and C++ is the OOP language of that era. Including statements on how C++ fits nicely with the OOP styles of web specs.

There’s always the option of contributing to Servo if you’re interested in Rust and browser engineering.

For the WSL part: that's one command in powershell/cmd and then a download from the Microsoft store. You won't find it challenging, there's not much more to it than that in 99% of cases (and if you do run into issues, there are probably better alternatives to trying to fix WSL anyway).

As for C++, Ladybird uses very modern C++ that makes it substantially easier to write reasonably safe code than the C++ of yore.

Still, as much as I would like to see the world move to safer languages, C++ is everywhere. Every major browser is written in it. It's not "unusable" in the slightest (though I certainly understand not wanting to learn C++ as an outsider at this point in time, it's a quite boring language in comparison and the C++ job market probably won't let you make use of modern language features that might make it interesting).

I would love to live in a world where projects with security risks like web browsers would "just" use Rust instead of C++ but you'll have to convince the people building the browser to spend their own time or their bosses' time to learn Rust first, and that's a tough sell.

There's Servo if you want to contribute to an open source browser in Rust. It looks like it can certainly use the help it you compare its development speed with Ladybird.

Unusable yet people have written a browser in it?

I don't know which bubble you are in, but C++ is nowhere near obsolete status. As much as want Rust to be adopted widely, that still hasn't happened, despite small-scale effort to sprinkle it in various projects.

> The second is that it's written in the obsolete and unusable language of C++.

Oh come on. There's nicer ways to say "I'm not good at it". It's OK you know, you can't be good at everything. Just don't make it other people's fault.

Those are two you-problems.