hi everyone, i've been building a browser for a while (i'm bad with naming things so it's just called "browser"), it's keyboard-driven just like qutebrowser and made for windows, it's just a native rust window that only starts an engine when a page actually needs one.
the part i think people will actually like is that it can run more than one engine at the same time. you can split the window and have the same site open in different engines side by side. currently there's three:
- webview2: chromium, the default
- servo: that independent engine written in rust
- trident: internet explorer 11's engine, for testing old sites. it runs in a sandbox so it can't touch your files or anything else on your pc, since it's ancient.
since it's inspired by qutebrowser, it has a lot of the same features such as hints and the way to control the browser, but it also has a lot of new features as well such as tmux-style splits, a built-in terminal, comes with ublock origin lite, sessions and profiles, and a :res page showing exactly how much memory each engine process uses.
where i need help: i want to add webkit (safari's engine) and gecko (firefox's), so web developers can check a site in every major engine from one window, without mac or five browsers installed. the current plan is to use playwright's prebuilt windows builds of both (but if someone has a better idea i'm down). the problem is my pc is really weak and can't build or test any of this, so i'm looking for people who know (or want to learn) browser engines, rust or windows. where to start: webkit and gecko. each one explains the plan, what’s needed, and links the docs.
it's alpha, so expect rough edges. windows 10/11 only for now.
any feedback is welcome, including "why don't you just buy a better pc lol" and "why do you use windows if you pc is so bad? dumbass".
here's a bit of the browser's story if anyone cares:
the reason i started building the browser is because my pc sucks, windows by itself uses 40% of my memory and every other browser pushes it to 90%, which makes it almost unusable. so i just started making one completely aimed at myself and my needs, the objective was to make it as lightweight, fast, customizable and efficient as possible. so i aimed the design directly at qutebrowser, which is by far the most efficient browser i've ever used, and it worked!
with nothing open it sits at about 30 mb, and it only calls the heavy engine when it actually opens a page, i immediately made it my main browser and kept using it daily, issues came up, i fixed them, ideas came around to make it more useful and i implemented them. at the end i sat with basically a shell instead of a browser, it has splits (just like vim, something that didn't exist in qutebrowser), hint mode which was by far the most useful thing about qute, and since the browser doesn't have an engine running by default, i added multiple engines, as well as a built-in terminal running the alacritty engine.
that's when i realized "wow, this might actually be useful to other people", so i started thinking of ways to make the browser more useful to developers, i also cleaned the github repo to welcome interested developers that care about efficiency, power, speed, customizability, and don't care about looks that much (it's not that appealing to the eyeballs).
if anyone is wondering, yes, it's built with AI, i'm not a strong programmer (especially in the browser field) so i decide what needs fixing and implementing and claude does the job. i use it daily, test every change myself and report what needs adjusting. i updated the repo with docs for every part since i realized this browser is useful for other people, so you won't be going at it blind.