Fabio Manganiello on Nostr: nprofile1q…9rfhv nprofile1q…zp9cg I still use Firefox on my mobile devices ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqszpwcw859u8ayyuf5gz6pxz2nsn9dnflcykevvn0xqcvjj9yu4jsl9rfhv (nprofile…rfhv) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqz64vrw2nzatdeucd0gkftmyywv5lwh9vzl8clj06ap5gxnfl04ss0zp9cg (nprofile…p9cg) I still use Firefox on my mobile devices (mostly because it’s the only mobile browser that allows extensions), and #Cromite for everything that usually requires PWAs (Mozilla’s support for PWAs is still outrageously primitive, and I feel like they’ve really run out of excuses).
The problem is that, even though Cromite is basically a version of the open Chromium browser minus all things Google, it’s still based on the same engine.
I feel the urge for a new rendering engine, but let’s admit that, given the complexity of today’s Web technologies, we shouldn’t expect a community-driven project to get to the point where it can compete with Blink (or even Gecko and WebKit) any time soon.
Btw WebKit-based browsers (like surf) could be an option in the meantime, but outside of Safari I don’t see much development happening on that front.
Unfortunately Mozilla lost this train long ago when it decided that it didn’t want to decouple Gecko excessively from Firefox, so it’s harder to build browsers on their engine than it is with Blink/WebKit (unless you just provide Firefox with a different menu and a different skin).
I would also rephrase this constraint:
And usable with uBlock Origin
As:
Committed to be compatible with Extensions Manifest V2, forever and without compromises
At the current stage even the browsers that have stated that they’ll keep supporting Manifest V2 (namely Firefox and Brave) have also added a “let’s see how feasible it is on the long run” as an asterisk.
Personally I wouldn’t mind using a Blink/WebKit-based browser, as long as it meets all the other requirements and, most of all, if it commits to support V2 forever.
The problem is that, even though Cromite is basically a version of the open Chromium browser minus all things Google, it’s still based on the same engine.
I feel the urge for a new rendering engine, but let’s admit that, given the complexity of today’s Web technologies, we shouldn’t expect a community-driven project to get to the point where it can compete with Blink (or even Gecko and WebKit) any time soon.
Btw WebKit-based browsers (like surf) could be an option in the meantime, but outside of Safari I don’t see much development happening on that front.
Unfortunately Mozilla lost this train long ago when it decided that it didn’t want to decouple Gecko excessively from Firefox, so it’s harder to build browsers on their engine than it is with Blink/WebKit (unless you just provide Firefox with a different menu and a different skin).
I would also rephrase this constraint:
And usable with uBlock Origin
As:
Committed to be compatible with Extensions Manifest V2, forever and without compromises
At the current stage even the browsers that have stated that they’ll keep supporting Manifest V2 (namely Firefox and Brave) have also added a “let’s see how feasible it is on the long run” as an asterisk.
Personally I wouldn’t mind using a Blink/WebKit-based browser, as long as it meets all the other requirements and, most of all, if it commits to support V2 forever.