> We also chose to build it the hard way by not forking Chromium.
Bad call, because it's genuinely too hard for someone the size of Kagi, as they've discovered.
There's room for a Chromium fork that has a better reputation than Brave. (I use Brave, and it's great, but I realise many people don't want to use it.)
The struggle is the blind opening of chrome, like most people probably just do without thinking. Unless you are really a hardcore frontend developer, you lose nothing by switching to Firefox (or non chrome/chromium browser). I operate both and for 95%, maybe even more, there is no difference. By switching you will put pressure on google to keep on the users good side.
There's also ungoogled-chromium and it uses similar set of patches: <a href="https://github.com/ungoogled-software/ungoogled-chromium" rel="nofollow">https://github.com/ungoogled-software/ungoogled-chromium
clivedup · · focus · HN ↗
Bad call, because it's genuinely too hard for someone the size of Kagi, as they've discovered.
There's room for a Chromium fork that has a better reputation than Brave. (I use Brave, and it's great, but I realise many people don't want to use it.)
ajdude · · focus · HN ↗
We need more rendering engines out there in the wild, as the situation with chrome's monopoly is already critically dire.
clivedup · · focus · HN ↗
Mozilla have more momentum, experience, and funding, but still struggle.
prox · · focus · HN ↗
aucisson_masque · · focus · HN ↗
I don’t see any more difficulty between being a chromium browser or being a WebKit browser.
TingPing · · focus · HN ↗
vascea · · focus · HN ↗
[1] <a href="https://github.com/imputnet/helium" rel="nofollow">https://github.com/imputnet/helium
pndy · · focus · HN ↗
dartharva · · focus · HN ↗
int_19h · · focus · HN ↗