I know most of the answers here, prefer Gecko over Chromium because Google is a monopoly, but honestly I would like to make the switch, the bad thing is that I still find the Firefox interface on Android old, I know it seems a bit silly to risk a little privacy for a comfortable and visually pleasing interface, but recently I saw that Chromium forks are even more secure than those using Gecko, that’s why I still use Cromite
I take this opportunity to say that possibly the solution to this is WebLibre, a browser based on Gecko which is exactly what I’m looking for, unfortunately still in alpha but from what I’ve seen it’s on the right track
And Cromite is my example of how the problem with Chrome is not the rendering engine tech, but the motivations of pthe people driving it. Cromite is an excellent alternative to gecko.
Back when I was very young, my software development philosophy was build your software on an Amiga 3000 and test it on an Amiga 500. Why? So that you can make it as efficient as possible while building it on the most user-friendly tools.
I still don’t understand why this is not a thing. Just because memory is cheap and CPUs are fairly cheap does not mean we should just go blindly using it all up so we can spend more money on the next more powerful set of CPUs and ram.
Memory is not cheap anymore, and won’t be for quite a while.
Admittedly, I’ve not been in the market recently. It is, however, the counter argument most frequently used to ignore the advice I stated.