Hacker News new | ask | show | jobs
by webprofusion 870 days ago
Great to see some competition still alive in browser engine development. See also Servo (previously part of Mozilla) https://servo.org/ - that and Ladybird are still very underdeveloped compared to every day browsers.

It's a huge shame that there are no nightly builds of ladybird to try out but I assume that's because they just don't want the bug reports (if everything doesn't work it's pointless getting random bugs filed).
4 comments
marginalia_nu 870 days ago
Last I tried Ladybird didn't take very long to build. This was admittedly sometime last year and it's likely slower now, but still. It's very far from a 9 hour chromium build.
link
niutech 863 days ago
Ladybird packages are in AUR: https://aur.archlinux.org/packages/ladybird-git, FreshPorts: https://www.freshports.org/www/ladybird and HaikuPorts: https://depot.haiku-os.org/ladybird
link
vmfunction 870 days ago
Don't forget WebKit. It leads to project such as https://surf.suckless.org
link
jraph 870 days ago
WebKit is established and controlled by the richest company of the world. Most websites make sure they work on it because hardware (exclusively) running it are widespread. Why should someone interested in new players care? Anyone knowing about Servo and Ladybird has most likely heard of it anyway.

(agreed, it is a credible alternative to Blink's dominance)

link
DiggyJohnson 869 days ago
Because it can be used to do cool things, has an interesting development history, and most importantly:

> it is a credible alternative to Blink's dominance

link
vmfunction 864 days ago
For me it is like:

WebKit -> Chrome

Bun -> Node/Deno

It is good to have competitions in Ecmascript landscape, even though it is currently a duopoly, but with introduction of AWS LLRT, and QuickJS, maybe small player can even have a say so in this. It would be good the big corp comply to the Ecmascript and Web API standard.

link
ripley12 869 days ago
IIRC there are no builds because forcing people to compile it themselves ensures that users (and people who file issues) have a certain amount of technical competency. Keeps life easier for maintainers, but will probably change if/when the project matures.
link