Some people don't want to use browsers based on #Chromium. And it is a choice as valid as any other. But one thing is clear: building a #browser engine from scratch is not a simple task.
Our team maintains and modifies the Chromium code constantly, both to add features and to get rid of #datacollection tools and other stuff added by #Google. And this is already complex enough.
On top of that, we also have to modify WebKit on #iOS - at least for the time being.
Here's a recent interview where CEO @jon talks about our choices and the challenge of going against #BigTech as a small company:
https://www.kode24.no/artikkel/kritiserer-google-men-bruker-chromium-urealistisk-a-lage-egen-motor/80646397
(It's in Norwegian but don't let that scare you! 😉)
Why do you think because nobody has made a new valid engine since almost 20 years? Do you think it’s easier to implement the Vivaldi features in Gecko? It isn’t, a lot of these won’t even work in a FF fork. Why do you think that most other browser are Chromium based? But, I see, that you are the expert, capable to develope a browser from scratch in a few days, you clown.
Why do you think because nobody has made a new valid engine since almost 20 years? Do you think it’s easier to implement the Vivaldi features in Gecko? It isn’t, a lot of these won’t even work in a FF fork. Why do you think that most other browser are Chromium based? But, I see, that you are the expert, capable to develope a browser from scratch in a few days, you clown.