replace with webpositive or chromium is meaning porting them to haiku and this is even bigger task… maybe you can ask firefox team dev and chromium to port their software to haiku… but seem they not interesting (yet)
I don’t like chrome, but if i had Firefox, the current one on Haiku, i would be delighted.
In terms of visual impact and user experience, they seem made for each other, but maybe I’m conditioned by my ideas. hehe
I ported the QuteBrowser web browser (based on Chromium/WebEngine) to Haiku. It’s a good alternative if anyone likes Vim-based keybindings integrated.
Hopefully it is still in the repos; I haven’t been using Haiku for a while now…
Maybe the way forward would be indeed to port an existing browser, instead of writing one.
2 replies
Porting chromium or firefox would likely be a similarly big task to porting webkit. Both of these browsers integrate badly with the OS, so the end experience would likely be worse, and we would throw away all our work on webkit. The webkit port also helps expose bugs in Haiku, or provoke new apis all native apps can use too, so the dev time is partly improving haiku directly aswell.