When I initially decided to drop Chrome, I moved to Brave because - as a chromium-based browser - it supported the same set of extensions I’d grown accustomed to.
That being said, the crypto stuff weirded me out enough that, once I’d weaned myself off the extensions, I switched to Firefox.
Chromium has metric shit tons of work done that seems to perform great. What I would love to see is for Mozilla to fork Chromium, staff it with enough people to maintain it, add/remove the features they feel are appropriate/inappropriate, and thus reuse the tons of free work Google and others have already done. As a software engineer, I don’t buy the argument that it’s easier to correctly implement every new web feature anew than maintaining a fork. Every large org that ships anything based on Android for example maintains a fork of an even bigger codebase. It’s not as complicated as people make it out to be. It’s not a new problem and there are strategies to manage it. If Mozilla does this, they’ll be able to play an active role in steering by far the biggest rendering engine’s direction, instead of playing opposition with no stake in it. Now downvote away! 😄
I dont know why anyone would leave chrome and land on something like brave.
If youre ditching chrome, which you should, go to an actual different browser and use Firefox.
Personal anecdote:
When I initially decided to drop Chrome, I moved to Brave because - as a chromium-based browser - it supported the same set of extensions I’d grown accustomed to.
That being said, the crypto stuff weirded me out enough that, once I’d weaned myself off the extensions, I switched to Firefox.
Chromium has metric shit tons of work done that seems to perform great. What I would love to see is for Mozilla to fork Chromium, staff it with enough people to maintain it, add/remove the features they feel are appropriate/inappropriate, and thus reuse the tons of free work Google and others have already done. As a software engineer, I don’t buy the argument that it’s easier to correctly implement every new web feature anew than maintaining a fork. Every large org that ships anything based on Android for example maintains a fork of an even bigger codebase. It’s not as complicated as people make it out to be. It’s not a new problem and there are strategies to manage it. If Mozilla does this, they’ll be able to play an active role in steering by far the biggest rendering engine’s direction, instead of playing opposition with no stake in it. Now downvote away! 😄