I would argue that rather than 'supporting many websites' Chromium has actually warped web development around its own goals. This is one of the effects that really turns me off of it. Google has pushed to make Chrome the OS of the internet.

> I want to build a web browser.

Mild nitpick but "web browser" and "rendering engine" and "JavaScript" are different.

Anybody can take WebKit and do some cool stuff on top in the UI and call it a "web browser".

At the end of the day, without patching to the HTML/CSS rendering engine, it's going to perform like every other WebKit based browser, right?

https://en.wikipedia.org/wiki/Comparison_of_browser_engines

I know Chromium uses Blink and not WebKit now.

Looks like Ladybird is based on https://en.wikipedia.org/wiki/SerenityOS "LibWeb"

That's all just rendering. You need to hook a JavaScript engine up to the rendering engine as well (with glue to the DOM from what I know?)

Chromium is Blink + V8, right?

Does Ladybird SerenityOS Libweb also do JavaScript?

> Browser with JavaScript, WebAssembly, and more (check the spec compliance for JS, CSS, and WASM)

It does. https://github.com/SerenityOS/serenity https://github.com/SerenityOS/serenity/tree/master/Userland/...

Ladybird, as part of the larger SerenityOS project, is building the browser UI, layout engine and JavaScript engine all on its own. That's what I referred to when I meant "web browser".

"Listen man, that's great and all, but all I wanna know is, how slow are you gonna be with patching them there vulns?!"