I think I like the idea, but the structure of the code doesn't look the best. What most sticks out to me is the "Managers" directory. I've seen similar patterns before, even at my current place of work, but they seem to correlate with less experienced implementations. For instance, I clicked on one of them randomly and already found an issue: https://github.com/nook-browser/Nook/blob/09a4c6957a2e9fd7c5...
I guess `www.` (and only `www.`) is always special, and the only TLDs with two components are `"co.uk", "co.jp", "com.au", "co.nz", "com.br"` ... I don't know how critical this "Manager" is (what even is a "boost"?), but a web browser should absolutely have a proper list of TLDs!
> Transparent code, permissive license, and a community-driven roadmap.
Which I was going to mention is contradictory, because the point of permissive licenses is that it does not have to be Free forever. But the license is actually GPLv3 instead. So still contradictory wording, but the "permissive" is the part that isn't correct :-)
I'm interested in seeing all the new browsers that will come out in the next few years that are based off Ladybird. Or alternatively what Ladybird will enable in terms of customization. I think the days of Chromium/WebKit/Gecko forks are numbered.
How is built-in ad blocking not the foremost priority? Brave and Comet both have it. uBlock Origin is not as effective as it used to be as of Manifest v3.
Zen (Firefox-based) has been really refreshing. You could probably accomplish the same thing with some user scripts and user CSS, but the concern with those has always been that they could break at any time with a new update. That shouldn't happen with a fork like Zen as they have control over updates.
An integrated experience. In the past I found that the vertical tab options in Firefox had the tabs duplicated across the side and the top, which I always found to be a subpar experience. Again, probably something you could accomplish with user.js and user.css but there's a good chance an update could break your modifications.
Seems quite similar to Zen's experience, except it seems to be missing folders (which I admittedly don't use often, but they're sometimes handy to group a Jira ticket with a PR, or similar). I'll probably still stick with Zen while it's around, and maybe I'll hop over to LibreWolf as I'm not too happy about Mozilla's recent stance on privacy.
I guess `www.` (and only `www.`) is always special, and the only TLDs with two components are `"co.uk", "co.jp", "com.au", "co.nz", "com.br"` ... I don't know how critical this "Manager" is (what even is a "boost"?), but a web browser should absolutely have a proper list of TLDs!
Is this sarcasm? The public suffix list will give some ideas for omissions: https://publicsuffix.org/list/public_suffix_list.dat
> Open-source forever
> Transparent code, permissive license, and a community-driven roadmap.
Which I was going to mention is contradictory, because the point of permissive licenses is that it does not have to be Free forever. But the license is actually GPLv3 instead. So still contradictory wording, but the "permissive" is the part that isn't correct :-)
I'm interested in seeing all the new browsers that will come out in the next few years that are based off Ladybird. Or alternatively what Ladybird will enable in terms of customization. I think the days of Chromium/WebKit/Gecko forks are numbered.
I'm going out on a limb here and betting they're numbered in the high thousands minimum.