By managing your Firefox settings through a user.js template, you avoid having settings silently changed without your knowledge or consent.
I was thinking on this today, the state of browsers and how big the web standard has gotten, and there really is no optimal choice. If you use something like LibreWolf or Mullvad, you're at the mercy of those smaller teams to keep up with releases and to not throw in the towel one day. But if you go upstream right to Firefox, there is so much decluttering and sanitizing one has to do that it necessitates tools like Arkenfox or Betterfox, plus a plethora of extensions.
Corporate developers like those heading Google's chrome team know that if they develop standards rapidly enough, that smaller potential competitors will be driven out of the race simply because they do not have the man power to keep up. Yes, I believe this is being done with intention and is not simply an convenient accident for Google.
When a codebase is sufficiently large, forks simply aren't good enough. Part of the value that huge software projects hold is in the institutional knowledge held by their active developers. A team of one or three or a dozen indie devs just isn't going to be able to wrangle the likes of Firefox or Chromium into their own sustainable endeavor which cuts the umbilical from Google or Mozilla, or be able to build anything equivalent from scratch.
It's such a sad state of affairs that we must treat our web browser as an adversary to be overcome. Once Google succeeds in killing off extension manifest v2, of course Mozilla will follow along like an obedient lapdog and we will need to scramble to find solutions that work outside of the hobbled extension framework.
What's everybody's current "plan B"?
I was thinking on this today, the state of browsers and how big the web standard has gotten, and there really is no optimal choice. If you use something like LibreWolf or Mullvad, you're at the mercy of those smaller teams to keep up with releases and to not throw in the towel one day. But if you go upstream right to Firefox, there is so much decluttering and sanitizing one has to do that it necessitates tools like Arkenfox or Betterfox, plus a plethora of extensions.
Corporate developers like those heading Google's chrome team know that if they develop standards rapidly enough, that smaller potential competitors will be driven out of the race simply because they do not have the man power to keep up. Yes, I believe this is being done with intention and is not simply an convenient accident for Google.
When a codebase is sufficiently large, forks simply aren't good enough. Part of the value that huge software projects hold is in the institutional knowledge held by their active developers. A team of one or three or a dozen indie devs just isn't going to be able to wrangle the likes of Firefox or Chromium into their own sustainable endeavor which cuts the umbilical from Google or Mozilla, or be able to build anything equivalent from scratch.
It's such a sad state of affairs that we must treat our web browser as an adversary to be overcome. Once Google succeeds in killing off extension manifest v2, of course Mozilla will follow along like an obedient lapdog and we will need to scramble to find solutions that work outside of the hobbled extension framework.
What's everybody's current "plan B"?
Statistics: Posted by Uptorn — 2024-02-06 22:54
